Intelligent subscription identification using transaction data

ABSTRACT

Intelligent subscription identification using transaction data is described. In an example, a computing system can receive transaction data associated one or more transactions between one or more merchants and one or more customers. Based at least in part on the transaction data, the computing system can determine that a first customer of the one or more customers purchased a first item at a first time and that a second customer of the one or more customers purchased a second item at a second time. The computing system can determine a recommendation to offer a subscription to enable the one or more customers to access a third item at a third time, send the recommendation to a device operable by a merchant of the one or more merchants, and associate an indication of the subscription with a profile of the merchant.

PRIORITY

This patent application is a continuation of, and claims priority to,U.S. patent application Ser. No. 16/574,004, filed on Sep. 17, 2019, andis fully incorporated by reference in its entirety herein.

TECHNICAL FIELD

A subscription is an arrangement for providing, receiving, or making useof something of a continuing or periodic nature. Rather than sellingitems (e.g., goods or services) individually, many merchants offercustomers subscriptions where customers pay a recurring price at regularintervals for access to a good or a service. Subscriptions enablemerchants predictable and constant revenue streams (e.g., during a termof a subscription). Further, subscriptions can increase brand loyalty.For customers, subscriptions offer conveniences such as discounts and/orrepeated fulfillment which can save time.

BRIEF DESCRIPTION OF THE DRAWINGS

Features of the present disclosure, its nature and various advantages,will be more apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings.

FIG. 1 illustrates an example environment for intelligently identifyinga subscription opportunity for a customer based at least in part ontransaction data as described herein.

FIG. 2A illustrates an example graphical user interface (GUI) forpresenting an offer for a subscription to a user as described herein.

FIG. 2B illustrates another example GUI for presenting an offer for asubscription to a user as described herein.

FIG. 3 illustrates an example environment for intelligently identifyinga subscription opportunity for a merchant based at least in part ontransaction data as described herein.

FIG. 4A illustrates an example GUI for presenting a recommendation tocreate a subscription to a user as described herein.

FIG. 4B illustrates an example GUI for presenting an indication that anitem is associated with a subscription as described herein.

FIG. 5 illustrates an example GUI for enabling users to managesubscription(s) as described herein.

FIG. 6 illustrates an example GUI for enabling users to managesubscription(s) as described herein.

FIG. 7 illustrates an example process for intelligently identifying asubscription opportunity (e.g., for a customer) based at least in parton transaction data as described herein.

FIG. 8 illustrates an example process for intelligently identifying asubscription opportunity (e.g., for a merchant) based at least in parton transaction data as described herein.

FIG. 9 illustrates an example process for automatically creating asubscription for a customer as described herein.

FIG. 10 illustrates an example process for automatically creating asubscription for a merchant as described herein.

FIG. 11 illustrates an example process for fulfilling an installment ofa subscription as described herein.

FIG. 12 illustrates an example process associated with additionaldetails for fulfilling an installment of a subscription as describedherein.

FIG. 13 illustrates an example process for monitoring subscriptioninteractions as described herein.

FIG. 14 illustrates an example process for determining pricing for asubscription as described herein.

FIG. 15 illustrates an example merchant ecosystem for facilitating,among other things, techniques described herein.

FIG. 16 illustrates additional details associated with individualcomponents of the merchant ecosystem described above in FIG. 15.

In the figures, the left-most digit(s) of a reference number identifiesthe figure in which the reference number first appears. The use of thesame reference numbers in different figures indicates similar oridentical items or features. The drawings are not to scale.

DETAILED DESCRIPTION

Techniques described herein are directed to intelligently identifyingopportunities for subscriptions for merchants and/or customers usingtransaction data associated with past transactions. In an example,transaction data associated with past transactions between merchants andcustomers can be analyzed to determine when an item (e.g., instancesthereof) is purchased at a substantially regular interval (e.g.,repeatedly). Based on determining that the item is purchased at asubstantially regular interval, a subscription opportunity can beidentified for a customer and/or a merchant. That is, techniquesdescribed herein can use itemized purchase history(s) of customer(s) todynamically generate and/or offer subscriptions on the fly (e.g., basedon what customers are purchasing). If a subscription is created for thecustomer, the customer can receive the additional items periodically(e.g., at intervals) without having to take subsequent action topurchase such items. That is, such items can be delivered (or otherwiseprovided) to the customer periodically (at a time after the subscriptionis established) based on the subscription. Additionally oralternatively, if a subscription is created for the merchant, themerchant can offer items to customers via a subscription. As such, themerchant can send (or otherwise provide) items to customers thatsubscribe to such items periodically (at a time after the subscriptionis established) without the customers needing to take subsequent actionto purchase such items.

In an example, a customer can purchase instances of an item (and/oritems of the same item type) from one or more merchants one time permonth. For example, the customer can purchase laundry detergent, whichmay or may not be associated with a same brand, from one or moremerchants approximately every 28-30 days. Such a buying pattern can beobserved from transaction data indicative of the customer's pasttransactions. Based on determining that the customer purchases laundrydetergent every 28-30 days, a service provider can identify asubscription opportunity for the customer. In at least one example, theservice provider can send an offer to the customer to prompt thecustomer to subscribe to receiving laundry detergent such that theservice provider and/or a merchant can deliver (or otherwise provide)the laundry detergent to the customer periodically without the customerhaving to take any other action (e.g., go to a brick-and-mortar store toshop for the laundry detergent and/or order the laundry detergent onlinevia an ecommerce channel). The frequency at which the customer receivesthe laundry detergent can be based on the substantially regular intervalobserved from the transaction data (e.g., 28-30 days) and/or can bespecified by the customer or the merchant. In some examples, the serviceprovider can bill the customer for the subscription in a lump sum (asingle payment paid at some frequency less than the frequency at whichthe laundry detergent is delivered (or otherwise provided) to thecustomer) or in association with each installment of the subscription(e.g., each time the laundry detergent is delivered (or otherwiseprovided) to the customer).

As another example, a customer can purchase coffee from a coffee shopeach morning. Such a buying pattern can be observed from transactiondata indicative of the customer's past transactions. Based ondetermining that the customer purchases coffee every morning from thesame coffee shop, a service provider can identify a subscriptionopportunity for the customer. In at least one example, the serviceprovider can send an offer to the customer to prompt the customer tosubscribe to coffee from the coffee shop. In an example, the coffee shopcan prepare the coffee each morning (e.g., at or near a same time) sothat the customer can pick up the coffee without having to order it thatmorning. In some examples, the customer can receive a prompt requestingthe customer to confirm or cancel an order for a particular day prior tothe coffee shop preparing the coffee for that day. In some examples, theservice provider can bill the customer for the subscription in a lumpsum (a single payment paid at some frequency less than the frequency atwhich the coffee is picked up by the customer) or in association witheach installment of the subscription (e.g., each time the coffee ispicked up by the customer).

In an additional or alternative example, transaction data can indicatethat one or more customers purchase instances of an item (and/or itemsassociated with a same item type) every 45-50 days. For example, one ormore customers can purchase dish soap every 45-50 days. The dish soapmay or may not be associated with the same brand and may or may not bepurchased from the same merchant. Based on determining that one or morecustomers purchase dish soap every 45-50 days, the service provider canprompt one or more merchants to create a subscription for dish soap suchthat customers can opt to subscribe to receiving dish soap periodicallywithout having to take any other action. The frequency at which thecustomers receive the laundry detergent can be based on the asubstantially regular interval observed from the transaction data (e.g.,45-50 days) and/or can be specified by the merchant or individualcustomers. That is, the service provider can prompt the one or moremerchants to establish a subscription and an indication of such can beassociated with an item (e.g., as presented via a graphical userinterface (GUI) associated with an online store and/or as presented inassociation with the item at a brick-and-mortar location). For customerswho subscribe to receiving dish soap, the merchant can cause dish soapto be delivered (or otherwise provided) to the customers periodically,as described above.

As described above, a subscription is an arrangement for providing,receiving, or making use of something of a continuing or periodicnature. Rather than selling items (e.g., goods or services)individually, many merchants offer customers subscriptions wherecustomers pay a recurring price at regular intervals for access to agood or a service. However, in conventional technologies, merchants optto offer only certain items via a subscription model, e.g., based onitem availability or knowledge that items are consumable (and thusrequire replacement). Many conventional technologies require merchantsto create a subscription plan. That is, conventional technologies areinefficient and cause friction for merchants. Many items that are ripefor subscriptions are overlooked and merchants don't take the time tocreate subscription plans because of the time and resources required.

Conventional technologies do not have access to transaction data asdescribed herein. That is, conventional technologies do not utilize anetwork-based merchant environment to generate and/or access transactiondata for multiple, different merchants (and customers) for determiningbuying patterns across multiple, different merchants (and customers).Such buying patterns can be used to intelligently identify subscriptionopportunities for merchants and/or customers, even for items that areotherwise not identified by a traditional subscription model. That is,techniques described herein can leverage transaction data—that caninclude item-level granularity—associated with multiple, differentmerchants (and/or customers) to generate customized and/or personalizedsubscription opportunities as opposed to the one-size-fits-allsubscriptions that are availed via conventional technologies. Forinstance, techniques described herein can identify subscriptionopportunities that enable customers to receive items at a frequencyparticular to their buying habits (or other customers similar to thecustomers) and/or enable merchants to provide items at a frequency thatis observed from buying habits of their customers and/or customers ofother or similar merchants. In some implementations, creatingcustomer-specific subscription flows can simplify network complexitiesand improve network efficiencies by replacing one-off/irregular purchasebehavior with predictable purchase behavior.

Techniques described herein offer various benefits to entitiesassociated with the network-based merchant environment. For instance, byproviding a recommendation to a merchant based on customer purchasebehavior, the merchant is more likely to convert a customer into arepeat customer or even a subscriber. As such, the merchant can receivean incremental increase in revenue based on ensuring that a customerpurchases an item repeatedly as opposed to running the risk of thecustomer forgetting to make their regular purchase. Furthermore, moresubscriptions enable recurring revenue and increased cash flow formerchants. Moreover, techniques described herein enable merchants todynamically offer subscriptions on the fly based on what their customersare purchasing, thereby reducing the friction of generating and/ormanaging subscriptions. For customers, techniques described hereinreduce friction associated with regular purchases and, in some examples,enable customers to subscribe to items or services through subscriptionsthat are customized and/or personalized for them. Additional benefitsand efficiencies are described throughout this disclosure.

FIG. 1 illustrates an example environment 100 for intelligentlyidentifying a subscription opportunity for a customer based at least inpart on transaction data. In FIG. 1, server(s) 102 can be associatedwith a service provider, that can provide one or more services, asdescribed below with reference to FIG. 15. In at least one example, theserver(s) 102 can communicate with user computing devices, such asmerchant device(s) 104 and customer device(s) 106, via network(s) 107.That is, the merchant device(s) 104 and the customer device(s) 106 arenetwork-connected devices that enable end users (e.g., merchant(s) 108and customer(s) 110, respectively) to access services provided by theservice provider (e.g., via the server(s) 102). In some examples, theservice provider can be a merchant of the merchant(s) 108 or a customerof the customer(s) 110. Additional details associated with the server(s)102, the user computing devices (e.g., 104, 106), and the network(s) 107are described below with reference to FIGS. 15 and 16.

In at least one example, the merchant(s) 108 and the customer(s) 110 canparticipate in transaction(s) 111, whereby a merchant provides an item(e.g., a good or service) to a customer via a brick-and-mortar store, amobile store (e.g., pop-up shop, food truck, etc.), online store,combinations of the foregoing, and so forth. In some examples, acustomer can purchase an item from a merchant for some consideration(e.g., the cost of the item). In other examples, a customer can acquirean item from a merchant via other means including, but not limited to,renting an item, borrowing an item, receiving an item for free, etc. Inat least one example, individual transaction(s) 111 can be associatedwith transaction data, which can indicate item(s) acquired via atransaction, descriptions of item(s) associated with the transaction, acost of the individual item(s), a total cost of the transaction, paymentdata for satisfying the total cost of the transaction, an identity of acustomer, an identity of a merchant, a date, time, and/or locationassociated with the transaction, and so on. Payment data, as describedherein, may include, but is not limited to, a name of the customer, anaddress of the customer, a type (e.g., credit, debit, etc.) of a paymentinstrument, a number associated with the payment instrument, averification value (e.g., PIN Verification Key Indicator (PVKI), PINVerification Value (PVV), Card Verification Value (CVV), CardVerification Code (CVC), etc.) associated with the payment instrument,an expiration data associated with the payment instrument, a primaryaccount number (PAN) corresponding to the customer (which may or may notmatch the number associated with the payment instrument), restrictionson what types of charges/debts may be made, etc.

The server(s) 102 can be associated with one or more functionalcomponents, which can include a subscription module 112 and a paymentprocessing module 114. The subscription module 112 can analyzetransaction data to identify subscription opportunities for merchant(s)108 and/or customer(s) 110 and/or can manage subscriptions. The paymentprocessing module 114 can process payment for the transaction(s) 111between merchant(s) 108 and/or customer(s) 110. Additional detailsassociated with the subscription module 112 and the payment processingmodule 114 are described below.

Additionally, the server(s) 102 can be associated with one or more datastores storing data including, but not limited to, profile(s) 116,inventory data 118, and transaction data 120.

In at least one example, the profile(s) 116 can store user profiles,which can include merchant profiles, customer profiles, and so on.

Merchant profiles can store, or otherwise be associated with, dataassociated with merchants, such as the merchant(s) 108. For instance, amerchant profile can store, or otherwise be associated with, informationabout a merchant (e.g., name of the merchant, geographic location of themerchant, operating hours of the merchant, employee information, etc.),a merchant category classification (MCC), item(s) offered for sale bythe merchant, hardware (e.g., device type) used by the merchant,transaction data associated with the merchant (e.g., transactionsconducted by the merchant, payment data associated with thetransactions, items associated with the transactions, descriptions ofitems associated with the transactions, itemized and/or total spends ofeach of the transactions, parties to the transactions, dates, times,and/or locations associated with the transactions, etc.), loaninformation associated with the merchant (e.g., previous loans made tothe merchant, previous defaults on said loans, etc.), risk informationassociated with the merchant (e.g., indications of risk, instances offraud, chargebacks, etc.), appointments information (e.g., previousappointments, upcoming (scheduled) appointments, timing of appointments,lengths of appointments, etc.), payroll information (e.g., employees,payroll frequency, payroll amounts, etc.), employee information,reservations data (e.g., previous reservations, upcoming (scheduled)reservations, interactions associated with such reservations, etc.),inventory data, customer service data, etc. The merchant profile cansecurely store bank account information as provided by the merchant(e.g., associated with a linked bank account). Further, the merchantprofile can store payment information associated with a paymentinstrument linked to an account maintained by the service provider.

Customer profiles can store, or otherwise be associated with, dataassociated with customers, such as the customer(s) 110. Such customerdata can include, but is not limited to, customer information (e.g.,name, phone number, address, banking information, etc.), customerpreferences (e.g., learned or customer-specified), purchase history data(e.g., identifying one or more items purchased (and respective iteminformation), payment instruments used to purchase one or more items,returns associated with one or more orders, statuses of one or moreorders (e.g., preparing, packaging, in transit, delivered, etc.), etc.),appointments data (e.g., previous appointments, upcoming (scheduled)appointments, timing of appointments, lengths of appointments, etc.),payroll data (e.g., employers, payroll frequency, payroll amounts,etc.), reservations data (e.g., previous reservations, upcoming(scheduled) reservations, reservation duration, interactions associatedwith such reservations, etc.), inventory data, customer service data,etc.

The inventory data 118 can store data items associated with items that amerchant has available for sale (or other form of acquisition).Inventory data 118 can additionally include information associated witheach item, such as item characteristics (e.g., size, color, volume,dimensions, scent, brand, etc.), quantity of an item, price of an item,whether a subscription is available for the item, a subscription price,etc. In at least one example, at least a portion of the inventory data118 can be mapped to, or otherwise associated with, individual merchantprofiles. That is, inventory data 118 of a particular merchant can bemapped to, or otherwise associated with, the profile of the particularmerchant.

The transaction data 120 can be associated with transactions processedby the service provider (e.g., the payment processing module 114) onbehalf of the merchant(s) 108. In at least one example, a data itemassociated with a transaction can indicate item(s) acquired via atransaction, descriptions of item(s) associated with the transaction, acost of the individual item(s), a total cost of the transaction, paymentdata for satisfying the total cost of the transaction, an identity of acustomer, an identity of a merchant, a date, time, and/or locationassociated with the transaction, and so on. In some examples, thetransaction data 120 can be associated with transactions that are notprocessed by the service provider. In such an example, the transactiondata can be accessed via a third-party source or system, for instance,via an application programming interface (API) or a software developerkit (SDK) that enables functionality described herein to be integratedinto third-party sources or systems. As described above, the transactiondata 120 can be associated with brick-and-mortar transactions, ecommerce(e.g., online) transactions, combinations of the foregoing, and thelike.

In at least one example, the subscription module 112 can analyzetransaction data 120 and can determine that a customer makes repeatpurchases of an item and/or items of an item type at a substantiallyregular interval. For the purpose of this discussion, a customer canmake “repeat purchases of an item” or “purchase an item repeatedly” suchthat the customer purchases additional instances of a same item (e.g.,Brand A toothpaste, Brand B coffee beans, etc.) more than one time. Forthe purpose of this discussion, “item type” is used to describe a classof items, wherein items in the class are substantially similar (e.g., asimilarity metric associated with such items, determined, for exampleusing a machine-trained data model(s), meets or exceeds a threshold).For example, laundry detergent associated with different brands, havingdifferent volumes (e.g., fluid ounces), different scents, differentcleaning capabilities, etc. may not be the same “item” per se, but maybe associated with the same “item type” (i.e., laundry detergent). Insome examples, a machine-trained data model can output a similarityscore or other metric indicative of a similarity between two items. Sucha similarity score can be used to classify items as a same item type.

In at least one example, the subscription module 112 can determine thatan item (e.g., instances thereof) and/or items of the same item type arepurchased by a customer at a substantially regular interval based atleast in part on determining, from the transaction data 120, that thecustomer purchases the item (e.g., instances thereof) and/or the itemsof the same item type (i) at a particular frequency and/or (ii) afterthe lapse of subsequent periods of time, wherein the subsequent periodsof time differ by less than a threshold. In at least one example, thesubscription module 112 can determine, based on the transaction data120, that a customer purchases a first item at a first time, a seconditem at a second time, and a third item at a third time. The first item,the second item, and the third item can be instances of a same item (oritem type). In at least one example, the first time, the second time,and the third time can be associated with a frequency indicative thatthe customer purchases instances of an item (or item type) at asubstantially regular interval. For example, the subscription module 112can determine that a customer purchases an item (e.g., instancesthereof) and/or items of the same item type at a particular rate (e.g.,one time per day, one time per month, one time per certain number ofdays, one time per week, etc.). In an additional or alternative example,a first period of time between the first time and the second time, and asecond period of time between the second time and the third time can besubstantially equal. In some examples, the intervals between purchasescan be equal. However, in some examples, the intervals between purchasesmay not be equal. For intervals to be “substantially regular,” adifference between individual intervals may be less than a thresholdsuch that the variation between the length of the intervals is minimal.As an example, the subscription module 112 can determine that thecustomer purchases an item (e.g., instances thereof) and/or items of thesame item type in a recurring fashion (e.g., occurring periodically orrepeatedly) after the lapse of some period of time (e.g., every 24hours, every 45 days, every 90 days, etc.).

In at least one example, the subscription module 112 can utilizemachine-trained data models to determine that an item (e.g., instancesthereof) and/or items of the same item type are purchased by a customerat a substantially regular interval and/or to otherwise identify apattern indicative of a recurring purchase. In additional or alternativeexamples, the subscription module 112 can utilize statistical models,heuristics, or other mechanisms for determining that an item (e.g.,instances thereof) and/or items of the same item type are purchased by acustomer at a substantially regular interval and/or to otherwiseidentify a pattern indicative of a recurring purchase.

While the preceding discussion relates to determining that a customerpurchases items in a pattern indicating that a customer is a candidatefor a subscription, in some examples, additional or alternative factorscan be considered to determine whether the customer is a candidate for asubscription. For instance, in an example, quantity (e.g., bulk vs.small size), cost (e.g., using coupons, discounts, or selecting a lessexpensive purchasing option), or the like can be indicative that acustomer is a candidate for a subscription. That is, in addition to thefrequency with which a customer purchases a same item and/or items of asame item type, the subscription module 112 can additionally oralternatively consider quantity, cost, etc. in determining that acustomer qualifies for a subscription.

In at least one example, based on determining that a customer purchasesan item (e.g., instances thereof) and/or items of the same item type ata substantially regular interval, the subscription module 112 candetermine that the customer qualifies for a subscription. In at leastone example, the subscription module 112 can present an offer to thecustomer to prompt the customer to set up a subscription. Such asubscription can enable the customer to access additional itemsperiodically without subsequently requesting such items. That is, thecustomer need not return to a brick-and-mortar store or online store topurchase another instance of an item associated with a subscription. Insome examples, the subscription module 112 can present such an offer viaa point-of-sale (POS) device of a merchant in association with atransaction being processed at the POS device. In an additional oralternative example, the subscription module 112 can present such anoffer via a device of a customer (e.g., a customer device), for examplein association with an ecommerce transaction and/or at some other time.In some examples, the offer can be presented via a graphical userinterface (GUI) that is associated with an actuation mechanism that,when actuated, causes the subscription to be set up via a singleinteraction with the GUI (e.g., a one-click subscription). In at leastone example, the offer can be associated with an incentive (e.g., adiscount, free shipping, etc.) to incentivize the customer to sign upfor a subscription. Responsive to a customer indicating a desire toestablish a subscription, the subscription module 112 can associate anindication of the subscription with a profile of the customer. Such anindication can cause the profile of the customer to be associated with asubscription that is associated with an “active” subscription status.

In some examples, based at least in part on the subscription beingestablished, the subscription module 112 can fulfill the subscriptionvia one or more fulfillment events, which can correspond to“installments.” In at least one example, the customer can specify apreferred fulfillment method (e.g., pick-up (e.g., from a particularmerchant and/or merchant(s) the customer frequents), ship to home,delivery, etc.) when the subscription is created and/or at a later time.In examples where an address is required (e.g., ship to home, delivery,etc.), the subscription module 112 can use the customer's address, if itis associated with a profile of the profile(s) 116, or the subscriptionmodule 112 can prompt the customer for their address prior to the firstfulfillment event. In some examples, the merchant can specify one ormore fulfillment methods. In at least one example, the interval of timebetween fulfillment events can be based, at least in part, on the“substantially regular interval” observed from previous transactions. Inalternative examples, the interval of time between fulfillment eventscan be specified by the customer and/or the merchant. That is, thefrequency at which the items are provided to the customer can beinformed based on patterns observed from the transaction data 120 and/orcan be specified by the customer and/or the merchant. In some examples,a subscription can be associated with consistent fulfillment events(e.g., items fulfilled at regular intervals). In other examples, asubscription can be associated with variable fulfillment events. In suchexamples, an item and/or item type can be fulfilled in a recurringpattern but may not be provided at regular intervals.

In at least one example, prior to a fulfillment event, the subscriptionmodule 112 can generate an order for an item associated with thesubscription. The subscription module 112 can reserve an item in aninventory of a merchant based at least in part on generating the order.The order can be associated with a total cost. The subscription module112, via the payment processing module 114, can determine that the costof the order is satisfied (e.g., via the processing of a payment inassociation with the fulfillment event or via a previous paymentassociated with the subscription), and the subscription module 112 canprocess the order. That is the subscription module 112 can cause theitem to be delivered (or otherwise provided) to the customer.

In at least one example, a customer can establish a subscription with anindividual merchant. In such an example, an indication of thesubscription can be associated with a profile of the merchant and thesubscription module 112 can fulfill the subscription using inventory ofthe merchant. In other examples, a customer can establish a subscriptionwith the service provider, and the subscription module 112 can fulfillthe subscription using inventory of one or more merchants associatedwith the service provider. That is, the service provider can be agnosticto which merchant it uses to fulfill an installment of a subscription(e.g., so long as the merchant can satisfy conditions of thesubscription such as item type, fulfillment date, fulfillment method,etc.). In some examples, the subscription module 112 can access andanalyze prices from different merchants and can purchase an item from amerchant associated with the lowest advertised price. In some examples,such a savings can be passed on to the customer. In other examples, theservice provider can collect the difference between the cost of theinstallment advertised to the customer and the cost of the item aspurchased from the merchant associated with the lowest advertised price.In some examples, where the subscription module 112 cannot find an itemfor a price lower than what is advertised to the customer as the cost ofthe installment, the service provider can pay the difference between thecost of the installment advertised to the customer and the cost of theitem as purchased from the merchant.

In at least one example, a customer can pay for the items associatedwith the subscription via a lump sum payment (a single payment paid atsome frequency less than the frequency at which items are delivered (orotherwise provided) to the customer) or in association with eachinstallment of the subscription (e.g., each time an item is delivered(or otherwise provided) to the customer). Fees associated withsubscriptions and/or installments associated therewith can be flat fees,custom fees, tiered fees, unit-based, etc. In some examples, the feescan be set by the service provider. In at least one example, thecustomer can set a range that the customer is willing to pay for asubscription and the subscription module 112 can identify a subscriptionassociated with a price within the provided range. In at least oneexample, if a customer is billed in association with an installment, thecustomer can be billed prior to an installment being fulfilled or afteran installment is fulfilled. In some examples, a customer may be billedprior to an installment being fulfilled, for example, if an item isassociated with a fixed fee and usage associated with such aninstallment is not likely to vary. Further, a customer may be billedafter an installment is fulfilled if, for example, the cost of thesubscription varies based on usage. In at least one example, paymentfrom a customer may be delayed until after a trial period (e.g., a freetrial period).

In some examples, a customer can have previously agreed to store paymentdata on file with the service provider (e.g., in a profile of theprofile(s) 116) and such payment data can be used, by the paymentprocessing module 114, to process payment for the items associated withthe subscription. In additional or alternative examples, a customer canprovide payment data for satisfying the cost of the items associatedwith the subscription at the time the subscription is created or inassociation with an installment of the subscription. In such examples,the payment data can be stored (e.g., by the service provider) forsubsequent use, by the payment processing module 114, to process paymentpaying for subsequent installments of the subscription.

In at least one example, the payment data can be associated with alinked bank account. In an additional or alternative example, thepayment data can be associated with an account that is maintained by theservice provider (e.g., generated from payment processing performed bythe service provider, from peer-to-peer payments facilitated by theservice provider, etc.). In some examples, funds associated with theaccount can be used, by the payment processing module 114, to processpayment for the cost of the items associated with the subscription atthe time the subscription is created and/or in association with eachinstallment. In an example where funds associated with the account areinsufficient to satisfy the cost of a subscription and/or an installmentassociated therewith, the payment processing module 114 can access fundsassociated with a linked bank account of the merchant and/or otherwiseprompt the customer to provide an alternative form of payment.

In some examples, the subscription module 112 can create a subscriptionwithout input from the customer. For instance, based at least in part ondetermining that a customer purchases an item (e.g., instances thereof)and/or items of the same item type repeatedly at a substantially regularinterval, the subscription module 112 can associate an indication of asubscription with a profile of the customer and can send the customer anitem after a lapse of a period of time based, at least in part, on thesubstantially regular interval. That is, the subscription module 112 canautomatically cause the profile of the customer to be associated with an“active” subscription status for the subscription. In some examples, thefirst installment can be offered to the customer for no charge (e.g.,the service provider pays a cost associated with the installment, themerchant provides the item at no cost, etc.) and the customer can becharged for subsequent installments. If the customer does not want tocreate a subscription for the item, the customer can cancel thesubscription, and, in some examples, the service provider can refundand/or credit the customer for the cost of the item (if the customer wascharged for the first installment). If the customer cancels thesubscription, the subscription module 112 can disassociate an indicationof the subscription from the profile of the customer and/or thesubscription can be associated with an “inactive” subscription status.In some examples, if a subscription is associated with a pre-paidservice that has an end date (e.g., the last day of the month, etc.),the subscription module 112 can refrain from dissociating the indicationof the subscription from the profile of the customer and/or associatingan “inactive” subscription status with the subscription until the enddate. That is, the subscription can remain active until the end date.

As an example, in FIG. 1, a portion 122 of the transaction data 120indicates a subset of transactions associated with a customer. Asillustrated, the customer purchases contact solution at a substantiallyregular interval, as highlighted by the transactions identified withboxes in FIG. 1. Per the portion 122 of the transaction data 120, thecustomer appears to purchase contact solution every 28-30 days. As such,the subscription module 112 can create a subscription for the contactsolution for the customer. In some examples, the subscription can becreated without input from the customer. In other examples, thesubscription can be created responsive to an indication that thecustomer desires to establish a subscription. In at least one example,responsive to establishing the subscription, the subscription module 112can send a subscription confirmation to the customer (e.g., a deviceassociated therewith) and, in some examples, associate an indication ofthe subscription with a profile of the customer. Furthermore, in atleast one example, the subscription module 112 can reserve inventory forfulfillment of one or more installments of the subscription. Additionaldetails are provided below.

FIG. 2A illustrates an example GUI 200 for presenting an offer for asubscription to a user as described herein. For instance, in at leastone example, the subscription module 112 can cause the GUI 200 to bepresented via a display of a device operable by a user. In someexamples, such a GUI 200 can be presented via one of the merchantdevice(s) 104. In additional or alternative examples, such a GUI 200 canbe presented via one of the customer device(s) 106.

In at least one example, the subscription module 112 can cause an offerfor a subscription to be associated with a virtual cart or other GUIpresented in association with a checkout flow of a transaction. Theitems being promoted for subscription may be in the customer's currentcart, customer's past carts or transaction history, or even carts ofsimilar customers. For instance, the GUI 200 can be presented while acustomer is checking out either at a brick-and-mortar POS or anecommerce POS. In at least one example, the subscription module 112 canreceive an identifier associated with a customer associated with avirtual cart or a transaction being processed at a POS. For example, acustomer can “log-in” to an account associated with an ecommerce POS ora customer can provide a loyalty number at a brick-and-mortar POS. In atleast one example, payment data can serve as an identifier of acustomer, which can be provided to satisfy a cost of a transaction. Insuch examples, the device receiving such an identifier (e.g., a customerdevice or a merchant device) can transmit the identifier to thesubscription module 112 and the subscription module 112 can access aportion of transaction data 120 associated with the customer, which canbe used for determining whether to offer the customer a subscription atthe POS. In some examples, such a determination can be made in nearreal-time. However, in other examples, the profile of the customer canbe associated with an indication regarding a subscription opportunity(e.g., that has been previously identified).

In additional or alternative examples, the subscription module 112 cancause an offer for a subscription to be presented at any other time(e.g., prior to, during, or after a transaction). In some examples, if asubscription is presented to a customer after a transaction, thesubscription module 112 can refund and/or credit the customer at least aportion of a previous purchase price for an item associated with thesubscription. That is, in at least one example, the subscription module112 can generate a subscription and retroactively provide benefits ofthe subscription to the customer.

In at least one example, the GUI 200 can include text element(s) 202that include an offer for a subscription and identifies the item(s)associated with the subscription. As illustrated in FIG. 2A, the offeris associated with a subscription for contact solution. The textelement(s) 202 can include a price associated with the item with andwithout the subscription, a frequency at which an installment of thesubscription occurs, an interval between installments, a quantity ofitems associated with an installment, etc. In at least one example, atleast some of the information (e.g., quantity, frequency ofinstallments, interval between installments, etc.) associated with thesubscription can be auto-populated based on customer buying patternsidentified from the portion 122 of the transaction data 120. In someexamples, the offer can be associated with an incentive (e.g., in FIG.2A, a discount), which can be included in the text element(s) 202.

In at least one example, the GUI 200 can include an actuation mechanism204 that, when actuated, can send an indication from the devicepresenting the GUI 200 to the server(s) 102. In at least one example,responsive to receiving such an indication, the subscription module 112can associate an indication of the subscription with a profile of thecustomer (e.g., in the profile(s) 116). That is, the profile of thecustomer can be associated with a subscription that is associated withan “active” subscription status (e.g., for the item).

In an additional or alternative example, the subscription module 112 cancause additional information to be presented via the GUI 200 prior toassociating the indication of the subscription with the profile of thecustomer. For instance, the subscription module 112 can prompt thecustomer to input a fulfillment method (e.g., pick-up (e.g., from aparticular merchant and/or merchant(s) the customer frequents), ship tohome, delivery, etc.), an address (if necessary and/or not alreadystored in association with a profile of the customer), payment data (ifnot already stored in association with a profile of the customer), inputand/or confirmation of quantity, frequency of installments, intervalbetween installments, etc. Responsive to providing necessaryinformation, the subscription module 112 can send a subscriptionconfirmation to the customer (e.g., a device associated therewith) and,in some examples, can reserve inventory for fulfillment of one or moreinstallments of the subscription.

In some examples, the GUI 200 can be presented via a user interface on adevice operable by a user, such as one of the merchant device(s) 104and/or the customer device(s) 106. In at least one example, such a userinterface can be presented via a web browser, or the like. In otherexamples, such a user interface can be presented via an application,such as a mobile application or desktop application, which can beprovided by the service provider, or which can be an otherwise dedicatedapplication. In some examples, the GUI 200 can be presented as a pushnotification, an email, a text message, or the like. In other examples,the customer can request the offer to be sent to their device from thePOS. These offers may be associated with an expiration date to encouragethe customers to accept subscriptions within a certain time period.

FIG. 2B illustrates an example GUI 206 for presenting an offer for asubscription to a user as described herein. In at least one example, thesubscription module 112 can cause an offer for a subscription to beassociated with a virtual cart or other GUI presented in associationwith a checkout flow of a transaction. For instance, the GUI 206 can bepresented while a customer is checking out either at a brick-and-mortarPOS or an ecommerce POS. As illustrated in FIG. 2B, the GUI 206 caninclude an actuation mechanism 208 that, when actuated, can send anindication from the device presenting the GUI 200 to the server(s) 102.In at least one example, responsive to receiving such an indication, thesubscription module 112 can associate an indication of the subscriptionwith a profile of the customer (e.g., in the profile(s) 116). That is,the profile of the customer can be associated with a subscription thatis associated with an “active” subscription status (e.g., for the item).

As described above, in some examples, the subscription module 112 cancause additional information to be presented via the GUI 206 (e.g.,price of item(s) associated with the subscription, fulfillmentfrequency, etc.) prior to associating the subscription with the profileof the customer. Moreover, in an additional or alternative example, thesubscription module 112 can prompt the customer to input a fulfillmentmethod (e.g., pick-up (e.g., from a particular merchant and/ormerchant(s) the customer frequents), ship to home, delivery, etc.), anaddress (if necessary and/or not already stored in association with aprofile of the customer), payment data (if not already stored inassociation with a profile of the customer), input and/or confirmationof quantity, frequency of installments, interval between installments,etc. Responsive to providing necessary information, the subscriptionmodule 112 can send a subscription confirmation to the customer (e.g., adevice associated therewith) and, in some examples, can reserveinventory for fulfillment of one or more installments of thesubscription.

The GUIs 200 and 206 are provided as example GUIs and should not beconstrued as limiting. GUIs can include additional or alternativeinformation, can be presented via additional or alternativeconfigurations, and/or can be output via additional or alternativeoutput mechanisms.

While FIGS. 1, 2A, and 2B describe examples where a single item isidentified for a subscription, in some examples, the subscription module112 can identify two or more items for a subscription. That is, in someexamples, the subscription module 112 can analyze the transaction data120 and can determine that one or more customers purchase two or moreitems (e.g., and/or items of corresponding item types) at asubstantially regular interval, and often together. In such an example,the subscription module 112 can offer a subscription for the two or moreitems, which can be bundled together to provide discounts and/or sharedfulfillment (e.g., can be picked-up together, delivered together, etc.).In some examples, bundled subscriptions (e.g., subscriptions associatedwith two or more items) can be fulfilled by a single merchant or two ormore merchants. Furthermore, in some examples, bundled subscriptions canbe fulfilled via different fulfillment options, and/or by differentcombination of merchants each time, e.g., based on availability, timing,cost restrictions, etc.

FIG. 3 illustrates an example environment 300 for intelligentlyidentifying a subscription opportunity for a merchant based at least inpart on transaction data. The environment 300 includes the same orsimilar devices and/or users as described above with reference toFIG. 1. FIG. 3, however, depicts a different portion 302 of thetransaction data 120 which is associated with a merchant of themerchant(s) 108. As illustrated in FIG. 3, an individual customer isshown as purchasing contact solution from the merchant at asubstantially regular interval (e.g., every 28-30 days). In at least oneexample, the subscription module 112 can generate a recommendation tosend to a merchant device of the merchant device(s) 104 to recommendthat the merchant set up or otherwise offer a subscription for contactsolution.

That is, in at least one example, the subscription module 112 cananalyze transaction data 120 and can determine that one or morecustomers purchase an item (e.g., instances thereof) and/or items of thesame item type at a substantially regular interval. In at least oneexample, the subscription module 112 can determine that an item (e.g.,instances thereof) and/or items of the same item type are purchased byone or more customers at a substantially regular interval based at leastin part on determining, from the transaction data 120, that the one ormore customers purchase the item (e.g., instances thereof) and/or theitems of the same item type (i) at a particular frequency and/or (ii)after the lapse of subsequent periods of time, wherein the subsequentperiods of time differ by less than a threshold. In at least oneexample, the subscription module 112 can determine, based on thetransaction data 120, that one or more customers purchase a first itemat a first time, a second item at a second time, and a third item at athird time. The first item, the second item, and the third item can beinstances of a same item (or item type). In at least one example, thefirst time, the second time, and the third time can be associated with afrequency indicative that the customer(s) purchase instances of an item(or item type) at a substantially regular interval. For example, thesubscription module 112 can determine that one or more customerspurchase an item (e.g., instances thereof) and/or items of the same itemtype at a particular rate (e.g., one time per day, one time per month,one time per certain number of days, one time per week, etc.). In anadditional or alternative example, a first period of time between thefirst time and the second time, and a second period of time between thesecond time and the third time can be substantially equal. In someexamples, the intervals between purchases can be equal. However, in someexamples, the intervals between purchases may not be equal. Forintervals to be “substantially regular,” a difference between individualintervals may be less than a threshold such that the variation betweenthe length of the intervals is minimal. As an example, the subscriptionmodule 112 can determine that one or more customers purchase an item(e.g., instances thereof) and/or the items of the same item type in arecurring fashion (e.g., occurring periodically or repeatedly) after thelapse of some period of time (e.g., every 24 hours, every 45 days, every90 days, etc.).

In at least one example, the subscription module 112 can utilizemachine-trained data models to determine that an item (e.g., instancesthereof) and/or items of the same item type are purchased by one or morecustomers at a substantially regular interval and/or to otherwiseidentify a pattern indicative of a recurring purchase. In additional oralternative examples, the subscription module 112 can utilizestatistical models, heuristics, or other mechanisms for determining thatan item (e.g., instances thereof) and/or items of the same item type arepurchased by one or more customers at a substantially regular intervaland/or to otherwise identify a pattern indicative of a recurringpurchase.

While FIG. 3 illustrates a single customer (e.g., Customer A),techniques described herein can utilize aggregated transaction data 120associated with multiple, different merchants and multiple, differentcustomers. In some examples, one or more customers can purchase the item(e.g., instances thereof) and/or the items of the same item type at asubstantially regular interval from the same merchant of the merchant(s)108 or different merchants of the merchant(s) 108.

In at least one example, based on determining that one or more customerspurchase an item (e.g., instances thereof) and/or items of the same itemtype at a substantially regular interval, the subscription module 112can generate a recommendation to recommend that a merchant set up orotherwise offer a subscription. In some examples, the subscriptionmodule 112 can present such a recommendation via a POS device of amerchant in association with a transaction being processed at the POSdevice. In an additional or alternative example, the subscription module112 can present such a recommendation via a device of a merchant (e.g.,a merchant device) at some other time. In some examples, the offer canbe presented via a GUI associated with an actuation mechanism that, whenactuated, causes the subscription to be set up via a single interactionwith the GUI (e.g., a one-click subscription).

In at least one example, the recommendation can be associated with anincentive (e.g., a discount, discounted service, supplementary service,etc.) to incentivize the merchant to create a subscription for the item.Furthermore, in some examples, the recommendation can be associated witha recommended price for the item (e.g., per installment, for a group ofinstallments, etc.), a recommended frequency for fulfilling installmentsof the subscription, a recommended interval between installments, arecommended quantity of items associated with each installment, etc.Responsive to a merchant indicating a desire to create a subscription,the subscription module 112 can associate an indication of thesubscription with a profile of the merchant (e.g., in the profile(s)116). In at least one example, an indication of the subscription can beassociated with an item in an inventory of the merchant, which isassociated with the profile of the merchant.

In some examples, the subscription module 112 can create a subscriptionwithout input from the merchant. For instance, based at least in part ondetermining that one or more customers purchase an item and/or item(s)of a same item type at a substantially regular interval, thesubscription module 112 can associate an indication of a subscriptionwith a profile of the merchant. That is, the subscription module 112 canautomatically associate an indication of the subscription with a dataitem corresponding to the item in the inventory data 118 (e.g., whichcan be associated with the profile of the merchant) and the indicationof the subscription can be associated with an “active” subscriptionstatus. If the merchant does not want to create a subscription for theitem, the merchant can cancel the subscription. If the merchant cancelsthe subscription, the subscription module 112 can disassociate thesubscription from the profile of the merchant and/or the subscriptioncan be associated with an “inactive” subscription status.

In at least one example, the payment processing module 114 can processpayments for items fulfilled via a subscription, as described above. Insome examples, revenue generated from payment for items associated withsubscriptions can be deposited into an account of the merchant which ismaintained by the service provider. In at least one example, such anaccount can be funded by revenue generated by transactions processed bythe payment processing module 114 on behalf of the merchant.

FIG. 4A illustrates an example GUI 400 for presenting a recommendationto create a subscription to a user as described herein. For instance, inat least one example, the subscription module 112 can cause the GUI 400to be presented via a display of a device operable by a merchant (e.g.,one of the merchant device(s) 104). In at least one example, the GUI 400can include text element(s) 402 that include a recommendation for asubscription and identifies the item(s) associated with thesubscription. As illustrated in FIG. 4A, the recommendation isassociated with a subscription for contact solution. The text element(s)402 can include a price associated with the item with and without thesubscription, a frequency at which an installment of the subscriptionoccurs, an interval between instalments, a quantity associated with eachinstallment, etc. In at least one example, one or more of the price, thefrequency, the interval, the quantity, etc. can be recommended based atleast in part on customer buying patterns observed from the transactiondata 120. In some examples, the recommendation can be associated with anincentive for the merchant, which can be included in the text element(s)402.

In at least one example, the GUI 400 can include an actuation mechanism404 that, when actuated, can send an indication from the devicepresenting the GUI 400 to the server(s) 102. In at least one example,responsive to receiving such an indication, the subscription module 112can generate a subscription and associate an indication of thesubscription with a profile of the merchant. In an additional oralternative example, the subscription module 112 can cause additionalinformation to be presented via the GUI 400 prior to generating thesubscription. For instance, the subscription module 112 can prompt themerchant to provide details associated with the subscription (e.g.,pricing, frequency, fulfillment options, etc.).

In some examples, the GUI 400 can be presented via a user interface on adevice operable by a merchant, such as one of the merchant device(s)104. In at least one example, such a user interface can be presented viaa web browser, or the like. In other examples, such a user interface canbe presented via an application, such as a mobile application or desktopapplication, which can be provided by the service provider, or which canbe an otherwise dedicated application. In some examples, the GUI 400 canbe presented as a push notification, an email, a text message, or thelike.

FIG. 4B illustrates an example GUI 406 for presenting an indication thatan item is associated with a subscription as described here. In at leastone example, if a merchant opts to set up or otherwise offer asubscription for an item, an indication of the subscription can bepresented in association with the item, for example, via a GUI 406associated with an online store of the merchant. The GUI 406 includestext element(s) 408 that are associated with item information, includinga cost of the item without a subscription or with a subscription, afrequency associated with fulfillment, etc. Further, the GUI 406 caninclude an actuation mechanism 410 that, when actuated, can enable acustomer to subscribe to receiving the item (e.g., contact solution). Insome examples, the GUI 406 (or a portion thereof) can be presented at abrick-and-mortar POS, for example, when a customer is purchasing theitem from the merchant (e.g., in association with a checkout flow of atransaction). In additional or alternative examples, the GUI 406 can bepresented via an online store or other ecommerce channel.

The GUIs 400 and 406 are provided as example GUIs and should not beconstrued as limiting. GUIs can include additional or alternativeinformation, can be presented via additional or alternativeconfigurations, and/or can be output via additional or alternativeoutput mechanisms.

While FIGS. 3, 4A, and 4B describe examples where a single item isidentified for a subscription, in some examples, the subscription module112 can identify two or more items for a subscription. That is, in someexamples, the subscription module 112 can analyze the transaction data120 and can determine that one or more customers purchase two or moreitems (e.g., and/or items of corresponding item types) at asubstantially regular interval, and often together. In such an example,the subscription module 112 can recommend that a merchant offer asubscription for the two or more items, which can be bundled together toprovide discounts and/or shared fulfillment (e.g., can be picked-uptogether, delivered together, etc.). In some examples, bundledsubscriptions (e.g., subscriptions associated with two or more items)can be fulfilled by a single merchant or two or more merchants.Furthermore, in some examples, bundled subscriptions can be fulfilledvia different fulfillment options.

FIG. 5 illustrates an example GUI 500 for enabling users to managesubscription(s) as described herein. In at least one example, customerscan subscribe to one or more subscriptions, which can be associated withone or more merchants. In at least one example, the subscription module112 can generate and/or cause to be presented a GUI 500 that enablescustomers to manage their subscriptions. In such an example, individualsubscriptions associated with the customer can be presented via the GUI500. In some examples, all subscriptions associated with a customerprofile, whether “active” or “inactive” can be presented via the GUI500. In other examples, “active” subscriptions associated with thecustomer profile can be presented via the GUI 500 and “inactive”subscriptions may not be presented via the GUI 500. In at least oneexample, the subscriptions presented via the GUI 500 can be associatedwith merchants that are associated with the service provider (e.g.,subscribe or otherwise use services of the service provider). Inadditional or alternative examples, the subscriptions presented via theGUI 500 can be associated with merchants that are not associated withthe service provider. In such examples, such subscriptions can be addedto the GUI 500 by the subscription module 112 based at least in part oninformation received via an API and/or SDK, or input by the customer.

In some examples, individual subscriptions can be associated withgraphical element(s) 502 (e.g., which can be an image, video, drawing,etc.) and text element(s) 504 that provide information associated withthe subscription. In at least one example, each subscription can beassociated with an actuation mechanism, such as actuation mechanism 506,which in FIG. 5 is illustrated as a link associated with the item ofeach subscription (e.g., “Wine”), that when actuated enables a customerto view additional details associated with the subscription, modifydetails(s) of the subscription (e.g., frequency of installments,interval between installments, quantity, etc.), cancel the subscription,etc. In at least one example, responsive to a customer actuating theactuation mechanism 506, a pop-up 508 can be presented that includesadditional details associated with the subscription and enables thecustomer to modify and/or cancel the subscription. While shown as apop-up 508, in additional or alternative examples, such information canbe presented via another GUI or another means of presentation.

In at least one example, the GUI 500 can enable a customer to add a newsubscription, for instance by browsing subscriptions that are availablefrom merchants associated with the service provider and/or merchantsthat are not associated with the service provider. In such an example,the customer can actuate an actuation mechanism 510 to request to browseadditional subscriptions. In some examples, when customers sign up formultiple subscriptions such customers can receive discounts or otherrewards and/or benefits.

In some examples, the GUI 500 can enable a customer to movesubscriptions between merchants. In at least one example, a customer maybe moving from a first location to a second location and the secondlocation may not have a merchant associated with a subscription of acustomer. In such an example, the subscription module 112 can identifyalternative merchants that are similar to the merchant to recommend tothe customer and can facilitate moving the subscription from themerchant to another merchant associated with the second location.Additionally or alternatively, a customer may choose to move asubscription to a different merchant due to the customer deciding tobundle multiple subscriptions with a single merchant, changedpreferences, etc. In both examples, the customer can interact with thepop-up 508 to modify the subscription.

Furthermore, in some examples, a customer can interact with the GUI 500to create a bundled subscription of two or more items. For example, insome examples, the customer can select multiple subscriptions andrequest to combine them or the customer can interact with the GUI 500 toadd item(s) to an existing subscription. In some examples, bundledsubscriptions (e.g., subscriptions associated with two or more items)can be fulfilled by a single merchant or two or more merchants.Furthermore, in some examples, bundled subscriptions can be fulfilledvia different fulfillment options.

FIG. 6 illustrates an example GUI 600 for enabling users to managesubscription(s) as described herein.

In at least one example, merchants can offer one or more subscriptionsfor customers. In at least one example, the subscription module 112 cangenerate and/or cause to be presented a GUI 600 that enables merchantsto manage their subscriptions. In such an example, individualsubscriptions associated with a merchant (e.g., Merchant A) can bepresented via the GUI 600. In some examples, all subscriptionsassociated with items of inventory of a merchant, whether “active” or“inactive” can be presented via the GUI 600. In other examples, “active”subscriptions can be presented via the GUI 600 and “inactive”subscriptions may not be presented via the GUI 600.

In some examples, individual subscriptions can be associated withgraphical element(s) 602 (e.g., which can be an image, video, drawing,etc.) and text element(s) 604 that provide information associated withthe subscription. In at least one example, each subscription can beassociated with an actuation mechanism, such as the actuation mechanism606, which in FIG. 6 is illustrated as a link associated with the itemof each subscription (e.g., “Shampoo & Conditioner”), that when actuatedenables a merchant to view additional details associated with thesubscription, modify aspect(s) of the subscription (e.g., frequency ofinstallments, interval between installments, price, quantity, etc.),cancel the subscription, etc. In at least one example, responsive to amerchant actuating the actuation mechanism 606, a pop-up 608 can bepresented that includes additional details associated with thesubscription and enables the customer to modify and/or cancel thesubscription. While shown as a pop-up 608, in additional or alternativeexamples, such information can be presented via another GUI or anothermeans of presentation.

In at least one example, the GUI 600 can enable a merchant to generate anew subscription. In some examples, the merchant can actuate anactuation mechanism 610 and manually input data associated with a newsubscription. In other examples, the merchant can actuate an actuationmechanism 610 to browse subscriptions that are recommended by thesubscription module 112.

The GUIs 500 and 600 are provided as example GUIs and should not beconstrued as limiting. GUIs can include additional or alternativeinformation, can be presented via additional or alternativeconfigurations, and/or can be output via additional or alternativeoutput mechanisms.

While FIGS. 1-6 are described with reference to subscriptions to items,and depict goods, techniques described herein can be application tosubscriptions for services as well. For example, the service providercan provide services (as described below) to users and such users cansubscribe to such services via techniques described herein. For example,the service provider can offer payment processing services, inventorymanagement services, catalog management services, business bankingservices, financing services, lending services, reservation managementservices, web-development services, payroll services, employeemanagement services, appointment services, loyalty tracking services,restaurant management services, order management services, fulfillmentservices, peer-to-peer payment services, onboarding services, identityverification (IDV) services, and so on. In such an example, merchantscan subscribe to such services via techniques described herein. Further,merchants and/or customers can offer and/or subscribe to subscriptionsfor additional or alternative services provided by other merchantsand/or users (e.g., house cleaning, hair services, spa services, carwashes, etc.).

FIGS. 7-14 are flowcharts showing example methods involving techniquesas described herein. The methods illustrated in FIGS. 7-14 are describedwith reference to FIGS. 1-6, 15, and 16 for convenience and ease ofunderstanding. However, the methods illustrated in FIGS. 7-14 are notlimited to being performed using components described in FIGS. 1-6, 15,and 16, and such components are not limited to performing the methodsillustrated in FIGS. 7-14.

The methods 700-1400 are illustrated as collections of blocks in logicalflow graphs, which represent sequences of operations that can beimplemented in hardware, software, or a combination thereof. In thecontext of software, the blocks represent computer-executableinstructions stored on one or more computer-readable storage media that,when executed by processor(s), perform the recited operations.Generally, computer-executable instructions include routines, programs,objects, components, data structures, and the like that performparticular functions or implement particular abstract data types. Theorder in which the operations are described is not intended to beconstrued as a limitation, and any number of the described blocks can becombined in any order and/or in parallel to implement the processes. Insome embodiments, one or more blocks of the process can be omittedentirely. Moreover, the methods 700-1400 can be combined in whole or inpart with each other or with other methods.

FIG. 7 illustrates an example process 700 for intelligently identifyinga subscription opportunity (e.g., for a customer) based at least in parton transaction data as described herein.

Block 702 illustrates analyzing transaction data of transactions betweenmerchant(s) and customer(s). As described above, a service provider canstore transaction data 120 associated with transactions processed by theservice provider (e.g., the payment processing module 114) on behalf ofthe merchant(s) 108. In at least one example, a data item associatedwith a transaction can indicate item(s) acquired via a transaction,descriptions of item(s) associated with the transaction, a cost of theindividual item(s), a total cost of the transaction, payment data forsatisfying the total cost of the transaction, an identity of a customer,an identity of a merchant, a date, time, and/or location associated withthe transaction, and so on. In some examples, the transaction data 120can be associated with transactions that are not processed by theservice provider. In such an example, the transaction data can beaccessed via a third-party source or system, for instance, via an API ora SDK that enables functionality described herein to be integrated intothird-party sources or systems.

In at least one example, the subscription module 112 can utilizemachine-trained data models to analyze the transaction data 102. Inadditional or alternative examples, the subscription module 112 canutilize statistical models, heuristics, or other mechanisms foranalyzing the transaction data 120.

Block 704 illustrates determining whether a customer purchases an itemand/or item(s) of a same item type at a substantially regular interval.In at least one example, the subscription module 112 can determine thatan item (e.g., instances thereof) and/or items of the same item type arepurchased by a customer at a substantially regular interval based atleast in part on determining, from the transaction data 120, that thecustomer purchases the item (e.g., instances thereof) and/or the itemsof the same item type (i) at a particular frequency and/or (ii) afterthe lapse of subsequent periods of time, wherein the subsequent periodsof time differ by less than a threshold. In at least one example, thesubscription module 112 can determine, based on the transaction data120, that a customer purchases a first item at a first time, a seconditem at a second time, and a third item at a third time. The first item,the second item, and the third item can be instances of a same item (oritem type). In at least one example, the first time, the second time,and the third time can be associated with a frequency indicative thatthe customer purchases instances of an item (or item type) at asubstantially regular interval. For example, the subscription module 112can determine that a customer purchases an item (e.g., instancesthereof) and/or items of the same item type at a particular rate (e.g.,one time per day, one time per month, one time per certain number ofdays, one time per week, etc.). In an additional or alternative example,a first period of time between the first time and the second time, and asecond period of time between the second time and the third time can besubstantially equal. In some examples, the intervals between purchasescan be equal. However, in some examples, the intervals between purchasesmay not be equal. For intervals to be “substantially regular,” adifference between individual intervals may be less than a thresholdsuch that the variation between the length of the intervals is minimal.As an example, the subscription module 112 can determine that thecustomer purchases an item (e.g., instances thereof) and/or items of thesame item type in a recurring fashion (e.g., occurring periodically orrepeatedly) after the lapse of some period of time (e.g., every 24hours, every 45 days, every 90 days, etc.).

In at least one example, the subscription module 112 can utilizemachine-trained data models to determine that an item (e.g., instancesthereof) and/or items of the same item type are purchased by a customerat a substantially regular interval and/or to otherwise identify apattern indicative of a recurring purchase. In additional or alternativeexamples, the subscription module 112 can utilize statistical models,heuristics, or other mechanisms for determining that an item (e.g.,instances thereof) and/or items of the same item type is purchased by acustomer at a substantially regular interval and/or to otherwiseidentify a pattern indicative of a recurring purchase.

As described above, in some example, factors other than frequency can beconsidered to determine whether the customer is a candidate for asubscription. For instance, in an example, quantity (e.g., bulk vs.small size), cost (e.g., using coupons, discounts, or selecting a lessexpensive purchasing option), or the like can be indicative that acustomer is a candidate for a subscription. That is, in addition to (oras an alternative to) the frequency with which a customer purchases asame item and/or items of a same item type, the subscription module 112can additionally or alternatively consider quantity, cost, etc. indetermining that a customer qualifies for a subscription.

Block 706 illustrates generating an offer for a subscription. In atleast one example, based on determining that a customer purchases anitem (e.g., instances thereof) and/or items of the same item type at asubstantially regular interval, the subscription module 112 candetermine that the customer is eligible and/or qualifies for asubscription. As such, the subscription module 112 can generate an offerfor the customer to prompt the customer to set up a subscription, forexample, to receive additional items (e.g., instances of the item)periodically without the customer needing to take an action tosubsequently receive such additional items. In at least one example, theoffer can be associated with an incentive (e.g., a discount, freeshipping, etc.).

Block 708 illustrates presenting the offer to the customer. In at leastone example, the subscription module 112 can present the offer to thecustomer to prompt the customer to set up a subscription. In someexamples, the subscription module 112 can present such an offer via aPOS device of a merchant in association with a transaction beingprocessed at the POS device. In an additional or alternative example,the subscription module 112 can present such an offer via a device of acustomer (e.g., a customer device), for example in association with anecommerce transaction and/or at some other time. In some examples, theoffer can be presented via a GUI that is associated with an actuationmechanism that, when actuated, causes the subscription to be set up viaa single interaction with the GUI (e.g., a one-click subscription).Non-limiting examples of GUIs for presenting such an offer to thecustomer are described above with reference to FIGS. 2A and 2B.

As described above, in at least one example, the subscription module 112can cause an offer for a subscription to be associated with a virtualcart or other GUI presented in association with a checkout flow of atransaction. For instance, the subscription module 112 can cause anoffer to be presented while a customer is checking out either at abrick-and-mortar POS or an ecommerce POS. In at least one example, thesubscription module 112 can receive an identifier associated with acustomer associated with a virtual cart or a transaction being processedat a POS. For example, a customer can “log-in” to an account associatedwith an ecommerce POS or a customer can provide a loyalty number at abrick-and-mortar POS. In at least one example, payment data can serve asan identifier of a customer, which can be provided to satisfy a cost ofa transaction. In at least one example, the device receiving such anidentifier (e.g., a customer device or a merchant device) can transmitthe identifier to the subscription module 112 and the subscriptionmodule 112 can cause an offer to be presented at the POS. In additionalor alternative examples, the subscription module 112 can cause an offerfor a subscription to be presented at any other time (e.g., prior to,during, or after a transaction).

Block 710 illustrates determining whether the customer indicates adesire to establish a subscription. In at least one example, asdescribed above with reference to FIGS. 2A and 2B, an offer can beassociated with an actuation mechanism, that when actuated, sends anindication from a device operable by a user (e.g., a merchant or acustomer) to the server(s) 102. Such an indication can indicate that thecustomer desires to establish a subscription. Additional or alternativeinputs can be provided to indicate that the customer desires toestablish a subscription. If the customer does not actuate the actuationmechanism (e.g., within a threshold period of time) or otherwiseindicates that he or she does not desire to establish a subscription,the subscription module 112 can refrain from associating an indicationof a subscription with a profile of the customer, as illustrated inblock 712. That is, the subscription module 112 can refrain fromcreating a subscription for the customer. In at least one example,responsive to the customer declining an offer for a subscription, such asubscription may not be presented to the customer again until after aprescribed amount of time has lapsed. In some examples, the past offers(and customer's responses) may be used to adjust future offers.

Block 714 illustrates determining and/or confirming details of asubscription. In at least one example, responsive to receiving anindication that the customer desires to establish a subscription, thesubscription module 112 can cause additional information to be presentedto the customer prior to associating the subscription with the profileof the customer. For instance, the subscription module 112 can promptthe customer to input a fulfillment method (e.g., pick-up (e.g., from aparticular merchant and/or merchant(s) the customer frequents), ship tohome, delivery, etc.), an address (if necessary and/or not alreadystored in association with a profile of the customer), payment data (ifnot already stored in association with a profile of the customer), etc.Furthermore, the subscription module 112 can prompt the customer toinput and/or confirm quantity per installment, frequency ofinstallments, interval between installments, etc. In some examples, atleast some of the details of the subscription can be determined based oncustomer buying patterns observed from the transaction data 120. Forexample, if the transaction data 120 indicates that a customer ships anitem to their home, the fulfillment method can be auto-populated to“ship to home.” Additionally or alternatively, the quantity, frequency,interval between installments, etc. can be auto-populated based oncustomer buying patterns observed from the transaction data 120. In someexamples, such buying habits can be associated with the customer (e.g.,personalized) or one or more other customers, which may be similar tothe customer (e.g., customized). Customers can be similar to one anotherif customer data associated with their profiles are associated with asimilarity score that meets or exceeds a threshold, for example.

Block 716 illustrates associating an indication of a subscription with aprofile of the customer. Responsive to a customer indicating a desire toestablish a subscription and/or determining and/or confirming details ofthe subscription, the subscription module 112 can associate anindication of the subscription with a profile of the customer. Such anindication can cause the profile of the customer to be associated with asubscription the is associated with an “active” subscription status(e.g., for the item). In at least one example, the subscription module112 can send a subscription confirmation to the customer (e.g., a deviceassociated therewith) and, in some examples, can reserve inventory forfulfillment of one or more installments of the subscription.

In at least one example, merchant(s) associated with the subscriptioncan have previously opted into a program for offering subscriptions. Inadditional or alternative examples, responsive to the details of thesubscription being determined, the subscription module 112 can send anindication of the subscription, and associated details, to one or moremerchants. In at least one example, a first-in-time merchant to respondcan be determined to be the merchant associated with the subscription.In additional or alternative examples, such merchants can bid on such asubscription and the subscription module 112 can select a highestbidding merchant. In at least one example, the subscription module 112can associate an indication of the subscription with a profile of themerchant selected for the subscription.

In some examples, the subscription module 112 can create a subscriptionwithout input from the customer (e.g., automatically), as shown by thedashed line from block 704 to block 716. For instance, based at least inpart on determining that a customer purchases an item and/or item(s) ofa same item type at a substantially regular interval, the subscriptionmodule 112 can associate an indication of a subscription with a profileof the customer, as illustrated in block 716. Additional details aredescribed below with reference to FIG. 8.

FIG. 8 illustrates an example process 800 for automatically creating asubscription for a customer as described herein.

Block 802 illustrates automatically associating a subscription with aprofile of a customer. In some examples, the subscription module 112 cancreate a subscription without input from the customer. For instance,based at least in part on determining that a customer purchases an item(e.g., instances thereof) and/or item(s) of a same item type at asubstantially regular interval, the subscription module 112 canassociate an indication of a subscription with a profile of the customerwithout prompting the customer to accept an offer for a subscription orotherwise take any other action to create the subscription. That is, thesubscription module 112 can automatically cause the profile of thecustomer to be associated with a subscription that is associated with an“active” subscription status (e.g., for the item). In some examples, thefirst installment can be offered to the customer for no charge (e.g.,the service provider pays the installment, the merchant provides theitem at no cost, etc.) and the customer can be charged for subsequentinstallments.

Block 804 illustrates determining whether the customer cancels thesubscription. If the customer does not want to create a subscription forthe item, the customer can cancel the subscription. In at least oneexample, the subscription module 112 can send a customer (e.g., a deviceassociated therewith) an option to cancel (e.g., in association with anotification of a first installment). For example, such an option can beprovided via a text message, email, push notification, etc. The customercan interact with the text message, email, push notification, etc. tocancel the subscription. In an additional or alternative example, thecustomer can access a hub, dashboard, or other GUI that enables thecustomer to manage his or her subscriptions and can request to cancelthe subscription via the hub, dashboard, or other GUI. An example ofsuch a GUI is provided in FIG. 5.

Block 806 illustrates determining whether the customer was charged for aportion of the subscription. In at least one example, if a subscriptionis not associated with a free trial period and if customer has storedhis or her payment data (e.g., card-on-file), the customer may becharged for the first installment of the subscription (e.g., if thecustomer does not cancel prior to the first installment). In at leastone example, if the customer does not want to create a subscription forthe item, the customer can cancel the subscription and if the customeris charged for the first installment, the service provider can refundand/or credit the customer for the cost of the item.

Block 808 illustrates disassociating an indication of the subscriptionfrom the profile of the customer and/or associating an “inactive”subscription status with the subscription. In at least one example, thesubscription module 112 can receive an indication that the customerdesires to cancel the subscription and, if the customer cancels thesubscription and the customer was not charged for a portion of thesubscription, the subscription module 112 can disassociate an indicationof the subscription from the profile of the customer and/or thesubscription can be associated with an “inactive” subscription status.In some examples, if a subscription is associated with a trial periodand/or a pre-paid service that has an end date (e.g., the last day ofthe month, etc.), the subscription module 112 can refrain fromdissociating the indication of the subscription from the profile of thecustomer and/or associating an “inactive” subscription status with thesubscription until the end date. That is, the subscription can remainactive until the end date.

Block 810 illustrates issuing a refund and/or credit to the customer. Inat least one example, the subscription module 112 can receive anindication that the customer desires to cancel the subscription and, ifthe customer was charged for a portion of the subscription, thesubscription module 112 can transfer funds corresponding to the portionof the subscription (e.g., a cost of an item associated with the firstinstallment) into an account of the customer. In some examples, thefunds can be deposited into a bank account of the customer that isassociated with the payment data stored in association with the serviceprovider (e.g., a linked bank account). In other examples, the funds canbe deposited into an account maintained by the service provider, asdescribed above. After the customer is refunded and/or credited, thesubscription module can disassociate the indication of the subscriptionfrom the profile of the customer and/or the subscription can beassociated with an “inactive” subscription status, as illustrated inblock 808.

In some examples, the subscription module 112 can proceed directly toblock 808 and disassociate the subscription from the profile of thecustomer and/or cause the subscription to be associated with an“inactive” subscription status (as shown by the dashed line from block804 to block 808). That is, in some examples, the subscription module112 may not consider whether a customer was charged prior todisassociating the subscription from the profile of the customer and/orcausing the subscription to be associated with an “inactive”subscription status.

Block 812 illustrates obtaining or confirming payment data of thecustomer. In at least one example, if the customer does not cancel thesubscription, the subscription module 112 can determine whether paymentdata is stored in association with a profile of the customer (e.g., inthe profile(s) 116). In some examples, such payment data can includeaccount information associated with a bank account linked to the profileof the customer. In other examples, the payment data can include accountinformation associated with an account maintained by the serviceprovider. In some examples, if payment data is stored in associationwith the profile of the customer, the subscription module 112 can promptthe customer to confirm that the customer would like to use the paymentdata to pay for the subscription. In other examples, the subscriptionmodule 112 can use the payment data without prompting the customer(e.g., if the customer has previously agreed that such payment data canbe used). If the payment data is not stored in association with theprofile, the subscription module 112 can prompt the customer to providepayment data for satisfying a cost of the transaction. In some examples,the subscription module 112 can prompt the customer to provide otherdetails associated with the subscription in association with obtainingor confirming their payment data.

In at least one example, prior to a customer providing payment dataand/or such payment data being processed (successfully), the profile ofthe customer can be associated with a subscription that is associatedwith a “pending” subscription status. If the payment data is notsuccessful, the profile of the customer may be associated with asubscription that is associated with an “in grace” subscription statusuntil the payment data is processed (successfully) or the customerbecomes delinquent, at which time the subscription module 112 canassociate an “inactive” subscription status with the subscription and/ordisassociate the indication of the subscription from the profile of thecustomer.

FIG. 9 illustrates an example process 900 for intelligently identifyinga subscription opportunity (e.g., for a merchant) based at least in parton transaction data as described herein.

Block 902 illustrates analyzing transaction data of transactions betweenmerchant(s) and customer(s). As described above, a service provider canstore transaction data 120 associated with transactions processed by theservice provider (e.g., the payment processing module 114) on behalf ofthe merchant(s) 108. In at least one example, a data item associatedwith a transaction can indicate item(s) acquired via a transaction,descriptions of item(s) associated with the transaction, a cost of theindividual item(s), a total cost of the transaction, payment data forsatisfying the total cost of the transaction, an identity of a customer,an identity of a merchant, a date, time, and/or location associated withthe transaction, and so on. In some examples, the transaction data 120can be associated with transactions that are not processed by theservice provider. In such an example, the transaction data can beaccessed via a third-party source or system, for instance, via an API ora SDK that enables functionality described herein to be integrated intothird-party sources or systems. In at least one example, thesubscription module 112 can analyze transaction data 120. In at leastone example, the subscription module 112 can utilize machine-traineddata models to analyze the transaction data 120. In additional oralternative examples, the subscription module 112 can utilizestatistical models, heuristics, or other mechanisms for analyzing thetransaction data 120.

Block 904 illustrates determining whether customer(s) purchase an itemand/or item(s) of a same item type at a substantially regular interval.That is, in at least one example, the subscription module 112 cananalyze transaction data 120 and can determine that one or morecustomers purchase an item (e.g., instances thereof) and/or items of thesame item type at a substantially regular interval. In at least oneexample, the subscription module 112 can determine that an item (e.g.,instances thereof) and/or items of the same item type are purchased byone or more customers at a substantially regular interval based at leastin part on determining, from the transaction data 120, that the one ormore customers purchase the item (e.g., instances thereof) and/or theitems of the same item type (i) at a particular frequency and/or (ii)after the lapse of subsequent periods of time, wherein the subsequentperiods of time differ by less than a threshold. In at least oneexample, the subscription module 112 can determine, based on thetransaction data 120, that one or more customers purchase a first itemat a first time, a second item at a second time, and a third item at athird time. The first item, the second item, and the third item can beinstances of a same item (or item type). In at least one example, thefirst time, the second time, and the third time can be associated with afrequency indicative that the customer(s) purchase instances of an item(or item type) at a substantially regular interval. For example, thesubscription module 112 can determine that one or more customerspurchase an item (e.g., instances thereof) and/or items of the same itemtype at a particular rate (e.g., one time per day, one time per month,one time per certain number of days, one time per week, etc.). In anadditional or alternative example, a first period of time between thefirst time and the second time, and a second period of time between thesecond time and the third time can be substantially equal. In someexamples, the intervals between purchases can be equal. However, in someexamples, the intervals between purchases may not be equal. Forintervals to be “substantially regular,” a difference between individualintervals may be less than a threshold such that the variation betweenthe length of the intervals is minimal. As an example, the subscriptionmodule 112 can determine that one or more customers purchase an item(e.g., instances thereof) and/or the items of the same item type in arecurring fashion (e.g., occurring periodically or repeatedly) after thelapse of some period of time (e.g., every 24 hours, every 45 days, every90 days, etc.).

In at least one example, the subscription module 112 can utilizemachine-trained data models to determine that an item type is purchasedby one or more customers at a substantially regular interval and/or tootherwise identify a pattern indicative of a recurring purchase. Inadditional or alternative examples, the subscription module 112 canutilize statistical models, heuristics, or other mechanisms fordetermining that an item type is purchased by one or more customers at asubstantially regular interval and/or to otherwise identify a patternindicative of a recurring purchase.

As described above, in some example, factors other than frequency can beconsidered to determine whether an item type is a candidate for asubscription. For instance, in an example, quantity (e.g., bulk vs.small size), cost (e.g., using coupons, discounts, or selecting a lessexpensive purchasing option), or the like can be indicative that an itemtype is a candidate for a subscription. That is, in addition to (or asan alternative to) the frequency with which customers purchase a sameitem and/or items of a same item type, the subscription module 112 canadditionally or alternatively consider quantity, cost, etc. indetermining that an item qualifies for a subscription.

Block 906 illustrates generating a recommendation for a subscription. Inat least one example, based on determining that one or more customerspurchase an item and/or item(s) of the same item type at a substantiallyregular interval, the subscription module 112 can generate arecommendation to recommend that a merchant set up or otherwise offer asubscription. Furthermore, in some examples, the recommendation can beassociated with a recommended price for the item (e.g., perinstallment), a recommended frequency for fulfilling installments of thesubscription, a recommended interval between installments, a recommendedquantity of items associated with each installment, etc. In at least oneexample, the recommended price, recommended frequency, recommendedinterval, recommended quantity, etc. can be based at least in part oncustomer buying patterns observed from the transaction data 120.

Block 908 illustrates presenting the recommendation to the merchant. Inat least one example, the subscription module 112 can present such arecommendation via a POS device of a merchant in association with atransaction being processed at the POS device. In an additional oralternative example, the subscription module 112 can present such arecommendation via a device of a merchant (e.g., a merchant device) atsome other time. In some examples, the recommendation can be presentedvia a GUI that is associated with an actuation mechanism that, whenactuated, causes the subscription to be set up via a single interactionwith the GUI (e.g., a one-click subscription). An example of such a GUIis described above with reference to FIG. 4A. In at least one example,the recommendation can be associated with an incentive (e.g., adiscount, discounted service, supplementary service, etc.) toincentivize the merchant to create a subscription for the item.Responsive to a merchant indicating a desire to create a subscription,the subscription module 112 can associate an indication of thesubscription with a profile of the merchant.

Block 910 illustrates determining whether the merchant indicates adesire to establish a subscription. In at least one example, asdescribed above with reference to FIG. 4A, a recommendation can beassociated with an actuation mechanism, that when actuated, sends anindication from a device operable by the merchant (e.g., one of themerchant device(s) 104) to the server(s) 102. Such an indication canindicate that the merchant desires to establish a subscription. Themerchant can provide additional or alternative inputs to indicate adesire to establish a subscription. If the merchant does not actuate theactuation mechanism (e.g., within a threshold period of time) orotherwise indicates that it does not desire to establish a subscription,the subscription module 112 can refrain from associating a subscriptionwith a profile of the merchant, as illustrated in block 912. That is,the subscription module 112 can refrain from creating a subscription forthe merchant.

Block 914 illustrates determining and/or confirming details of asubscription. In at least one example, responsive to receiving anindication that the merchant desires to establish a subscription, thesubscription module 112 can cause additional information to be presentedto the customer prior to associating the subscription with the item inan inventory of the merchant. For instance, the subscription module 112can prompt the merchant to identify possible fulfillment methods (e.g.,pick-up, ship to home, fulfillment, etc.), input and/or confirmquantity, frequency of installments, intervals between installments,etc. In some examples, at least some of the details of the subscriptioncan be determined based on customer buying patterns observed from thetransaction data 120.

In at least one example, the subscription module 112 can access dataassociated with the merchant and/or other merchants associated with theservice provider to recommend details associated with the subscription.For example, the subscription module 112 can access inventory of amerchant to determine a price for the subscription. In some examples,the subscription module 112 can consider subscriptions offered by othermerchants (e.g., for the same or similar item) and can recommend a pricebased on such subscriptions. In at least one example, the subscriptionmodule 112 can recommend a price within a price range for which amerchant agrees to offer a subscription. Further, in some examples, thesubscription module 112 can generate a confidence score indicatingwhether a subscription is likely to lead to increased sales, revenue,repeat customers, etc. In at least one example, subscriptioninteractions of customer(s) and/or merchant(s) can be used to generatethe confidence score.

Block 916 illustrates associating an indication of a subscription with aprofile of the merchant. Responsive to a merchant indicating a desire tocreate a subscription, the subscription module 112 can associate anindication of the subscription with a profile of the merchant. That is,the subscription module 112 can associate an indication of thesubscription with a data item corresponding to the item in the inventorydata 118 (e.g., which can be associated with the profile of themerchant) and the indication of the subscription can be associated withan “active” subscription status. In at least one example, thesubscription module 112 can send a subscription confirmation to themerchant (e.g., a device associated therewith) and, in some examples,can reserve inventory for fulfillment of one or more installments of thesubscription.

In some examples, the subscription module 112 can create a subscriptionwithout input from the merchant, as shown by the dashed line from block904 to block 916. For instance, based at least in part on determiningthat customer(s) purchase an item and/or item(s) of a same item type ata substantially regular interval, the subscription module 112 canassociate an indication of the subscription with a profile of themerchant, as illustrated in block 916. Additional details are describedbelow with reference to FIG. 10.

FIG. 10 illustrates an example process 1000 for automatically creating asubscription for a merchant as described herein.

Block 1002 illustrates automatically associating an indication of thesubscription with a profile of the merchant. In some examples, thesubscription module 112 can create a subscription without input from themerchant. For instance, based at least in part on determining that oneor more customers purchase an item (e.g., instances thereof) and/oritem(s) of a same item type at a substantially regular interval, thesubscription module 112 can associate an indication of a subscriptionwith an item in an inventory of the merchant. That is, the subscriptionmodule 112 can automatically associate an indication of the subscriptionwith a data item corresponding to the item in the inventory data 118(e.g., which can be associated with the profile of the merchant) and theindication of the subscription can be associated with an “active”subscription status.

Block 1004 illustrates determining whether the merchant cancels thesubscription. If the merchant does not want to create a subscription forthe item, the merchant can cancel the subscription. In at least oneexample, the subscription module 112 can send a merchant (e.g., a deviceassociated therewith) an option to cancel (e.g., in association with anotification of a first installment). For example, such an option can beprovided via a text message, email, push notification, etc. The merchantcan interact with the text message, email, push notification, etc. tocancel the subscription. In an additional or alternative example, themerchant can access a hub, dashboard, or other GUI that enables themerchant to manage its subscriptions and can request to cancel thesubscription via the hub, dashboard, or other GUI. An example of such aGUI is provided above with respect to FIG. 6.

Block 1006 illustrates disassociating an indication of the subscriptionfrom the profile of the merchant and/or associating an “inactive” statuswith the subscription. In at least one example, the subscription module112 can receive an indication that the merchant desires to cancel thesubscription and, if the merchant cancels the subscription, thesubscription module 112 can disassociate the indication of thesubscription from the profile of the merchant and/or the subscriptioncan be associated with an “inactive” status.

In at least one example, if the merchant cancels the subscription, thesubscription module 112 can move the subscription to another merchantthat is similar to the merchant and/or offers the same or a similaritem. In such an example, customer(s) who have subscribed to thesubscription can still receive items via a subscription (even though theitems are being received by a different merchant). In some examples,such a move can be communicated to the customer(s). In other examples,the customer(s) may not know that a different merchant is fulfillingtheir subscription.

Block 1008 illustrates obtaining or confirming details of thesubscription. In at least one example, based at least in part on themerchant opting not to cancel the subscription, the subscription module112 can prompt the merchant to input and/or confirm details associatedwith the subscription. For instance, the subscription module 112 canprompt the merchant to provide details associated with the subscription(e.g., pricing, frequency, fulfillment options, etc.).

FIG. 11 illustrates an example process 1100 for fulfilling aninstallment of a subscription as described herein.

Block 1102 illustrates generating an order associated with a fulfillmentevent corresponding to an installment of a subscription. In at least oneexample, in anticipation of a fulfillment event associated with aninstallment of a subscription, the subscription module 112 can generatean order associated with the installment of the subscription. In atleast one example, the order can indicate an item, a date forfulfillment, and instructions for fulfillment. In at least one example,the item can be an instance of an item (and/or item type) that gave riseto the subscription described herein.

Block 1104 illustrates determining whether the item associated with theorder is available via a merchant. In at least one example, thesubscription module 112 can determine whether the item associated withthe order is available in an inventory of a merchant and can befulfilled on (or near) the date for fulfillment in compliance with theinstructions for fulfillment associated with the order. If an item isavailable from the merchant, the process 1100 can proceed to process1200 described below with reference to FIG. 12. If an item is notavailable from the merchant, the process 1100 can proceed to block 1106.

Block 1106 illustrates determining whether the subscription isassociated with the service provider or the merchant. In at least oneexample, a customer can establish a subscription with an individualmerchant. In such an example, an indication of the subscription can beassociated with a profile of the merchant and the subscription module112 can fulfill the subscription using inventory of the merchant. Inother examples, a customer can establish a subscription with the serviceprovider, and the subscription module 112 can fulfill the subscriptionusing inventory of one or more merchants associated with the serviceprovider. That is, the service provider can be agnostic to whichmerchant it uses to fulfill fulfillment of an item to the customer(e.g., so long as the merchant can satisfy conditions of thesubscription such as item type, fulfillment date, fulfillment method,etc.).

Block 1108 illustrates determining whether an item associated with theorder is available via another merchant. If the subscription is with theservice provider, the subscription module 112 can look to inventory ofanother merchant to determine whether the item associated with the orderis available in an inventory of the other merchant and can be fulfilledon (or near) the date for fulfillment in compliance with theinstructions for fulfillment associated with the order. If an item isavailable from the other merchant, the process 1100 can proceed toprocess 1200 described below with reference to FIG. 12.

Block 1110 illustrates sending a notification to the customer. In atleast one example, if the subscription is with the merchant and themerchant cannot fulfill the order, the subscription module 112 can senda notification to the customer (e.g., a device associated therewith).Further, if the subscription is associated with the service provider,the subscription module 112 can look to inventories of other merchantsto fulfill the order. However, if no other merchant associated with theservice provider can fulfill the order, the subscription module 112 cansend a notification to the customer (e.g., a device associatedtherewith). In some examples, the notification can be sent via textmessage, email, push notification, or the like. In at least one example,the notification can inform the customer that the installment is unableto be fulfilled. In some examples, the notification can include anincentive for the customer (e.g., to compensate for the inconvenience,to incentivize the customer not to cancel the subscription, etc.). In anadditional or alternative example, the notification can include anindication that the installment is able to be fulfilled, but suchfulfillment may be delayed. In some examples, the notification caninclude an option for an alternate item, which may be different than theitem associated with the subscription but is substantially similar tothe item. For example, the alternate item may be associated with adifferent brand, a different volume, a different size, etc. In someexamples, the alternate item may be associated with a different merchantthan the merchant with whom the subscription is associated.

FIG. 12 illustrates an example process 1200 associated with additionaldetails for fulfilling an installment of a subscription as describedherein.

Block 1202 illustrates reserving, in association with an orderassociated with a fulfillment event of a subscription, an item in aninventory of a merchant. Based at least in part on determining that amerchant can fulfill the order, the subscription module 112 can send arequest (e.g., to the merchant) to reserve the item in the inventory ofthe merchant. In at least one example, when an item is reserved it canbe associated with an indication of such in the inventory data 118. Insome examples, an order can be associated with a single item. In otherexamples, an order can be associated with multiple items, for example,in association with a bundled subscription.

Block 1204 illustrates determining whether the cost of at least the itemhas been satisfied. In at least one example, a customer can pay foritems associated with the subscription via a lump sum payment (a singlepayment paid at some frequency less than the frequency at which itemsare delivered (or otherwise provided) to the customer) or in associationwith each installment of the subscription (e.g., each time an item isdelivered (or otherwise provided) to the customer). Fees associated withsubscriptions and/or installments associated therewith can be flat fees,custom fees, tiered fees, unit-based, etc. In some examples, a customercan provide payment data for satisfying the cost of the items associatedwith the subscription at the time the subscription is created and canpay for the cost of the subscription in a lump sum payment (a singlepayment paid at some frequency less than the frequency at which itemsare delivered (or otherwise provided) to the customer). In at least oneexample, if the cost of at least the item has been paid in associationwith the subscription at the time the subscription is created, thepayment processing module 114 can notify the subscription module 112 andthe subscription module 112 can process the order, as illustrated inblock 1206.

Block 1206 illustrates processing the order. In at least one example,the subscription module 112 can send a fulfillment instruction to themerchant to fulfill the order. In some examples, the fulfillmentinstruction can be associated with shipping instructions, a pre-madeshipping label, etc. In additional or alternative examples, thesubscriber module 112 can recommend packaging for the item and/or caninclude tips regarding facilitating a frictionless pick-up process(e.g., security considerations, skip-the-line options, etc.).

Block 1208 illustrates accessing payment data associated with a customerto whom the subscription corresponds. In at least one example, thepayment processing module 114 can receive an instruction to processpayment for the order. The payment processing module 114 can access theprofile(s) 116 to determine whether a profile of the customer isassociated with payment data.

In some examples, a customer can have previously agreed to store paymentdata on file with the service provider (e.g., in a profile of theprofile(s) 116) and such payment data can be used, by the paymentprocessing module 114, to process payment for the items associated withthe subscription. In additional or alternative examples, a customer canprovide payment data for satisfying the cost of the items associatedwith the subscription at the time the subscription is created or inassociation with an installment of the subscription. In such examples,the payment data can be stored (e.g., by the service provider) forsubsequent use, by the payment processing module 114, to process paymentpaying for subsequent installments of the subscription. In suchexamples, if the profile is associated with payment data, the paymentprocessing module 114 can access the payment data and can processpayment for at least the cost of the item, as illustrated in block 1210.In at least one example, payment data can be provided, saved, and/orused in association with any POS or ecommerce interactions where theservice provider is the payment processor.

If the profile of the customer is not associated with payment data, thepayment processing module 114 can prompt the customer for payment data,unless the subscription module 112 has indicated that the customer neednot pay for the order (e.g., the first installment, etc.). Uponreceiving payment data from the customer, the payment processing module114 can process payment for at least the cost of the item, asillustrated in block 1210.

Block 1212 illustrates determining whether the cost of at least the itemis satisfied by the payment data. In at least one example, the paymentprocessing module 114 can determine whether an account associated withthe payment data is sufficient to satisfy a cost of at least the item.For example, the payment processing module 114 can send an authorizationrequest to a payment service associated with the payment data, which maybe associated with a linked bank account, a credit card, etc. Thepayment service can provide a response to the request that indicateswhether an account associated with the payment data has enough funds tosatisfy the cost of at least the item. If the account has sufficientfunds, the authorization request can be approved and the paymentprocessing module 114 can notify the subscription module 112. Thesubscription module 112 can then process the order, as illustrated inblock 1206. If the authorization request is not approved (e.g.,declined), the payment processing module 114 can send a notification tothe customer to inform the customer that the payment data is notapproved and/or the cost of at least the item is not satisfied. In someexamples, the notification can prompt the customer to provide updatedpayment data.

In some examples, the payment data can be associated with an accountmaintained by the service provider. In such examples, the paymentprocessing module 114 can access the account maintained by the serviceprovider to determine whether the account is associated with sufficientfunds to satisfy the cost of at least the item. If the account hassufficient funds, the payment processing module 114 can notify thesubscription module 112. The subscription module 112 can then processthe order, as illustrated in block 1206. If the authorization request isnot approved (e.g., declined), the payment processing module 114 cansend a notification to the customer to inform the customer that thepayment data is not approved and/or the cost of at least the item is notsatisfied. In some examples, the notification can prompt the customer toprovide updated payment data.

In at least one example, the payment processing module 114 can processpayments for items fulfilled via a subscription, as described above. Insome examples, revenue generated from payment for items associated withsubscriptions can be deposited into an account of the merchant which ismaintained by the service provider. In at least one example, such anaccount can be funded by revenue generated by transactions processed bythe payment processing module 114 on behalf of the merchant.

FIG. 13 illustrates an example process 1300 for monitoring subscriptioninteractions as described herein.

Block 1302 illustrates monitoring subscription interactions ofcustomer(s) and/or merchant(s). In at least one example, after asubscription has been created for a customer or a merchant, thesubscription module 112 can monitor interactions between thesubscription and the customer or the merchant. In some examples,customer(s) and/or merchant(s) can modify and/or cancel theirsubscription(s) via GUIs, such as those described above with referenceto FIGS. 5 and 6. In at least one example, a customer may request todecrease the frequency at which the customer receives an installment, ora merchant may reduce a number of subscriptions available. Suchinteractions can be monitored by the subscription module 112.

Block 1304 illustrates determining whether a customer or a merchant islikely to cancel a subscription. In at least one example, thesubscription module 112 can analyze subscription interactions and canpredict when a customer or a merchant is likely to cancel asubscription. In such an example, the subscription module 112 canutilize machine-trained data models, statistical models, heuristics, orother mechanisms for determining that a customer or a merchant is likelyto cancel a subscription. For instance, subscription interactions can bemonitored and the subscription module 112 can output a score indicativeof a likelihood that a customer or a merchant is going to cancel asubscription. If the score meets or exceeds a threshold, thesubscription module 112 can determine that the customer or the merchantis likely to cancel the subscription.

Block 1306 illustrates sending an offer to the customer or the merchant,wherein the offer is associated with an incentive. Based at least inpart on determining that the customer or the merchant is likely tocancel a subscription, the subscription module 112 can send an offer tothe customer or the merchant. In at least one example, the offer can beassociated with an incentive. For example, the incentive for thecustomer can be a discount associated with the subscription. Or, theincentive for the merchant can be access to a service for a discountedrate. In any event, the incentive can seek to discourage the customer orthe merchant from cancelling the subscription. In at least one example,the offer can be sent via email, text message, push notification, or thelike. Furthermore, in some examples, such an offer can be presented viaa GUI, such as the GUIs described above with reference to FIGS. 5 and 6.

If the subscription module 112 determines that a customer or a merchantis not likely to cancel a subscription, the subscription module 112 cancontinue to monitor subscription interactions, as illustrated in block1302.

In some examples, if a customer or a merchant cancels a subscription,the subscription module 112 can send an offer to re-subscribe to asubscription at a time after the customer or the merchant cancels thesubscription. In at least one example, the offer can be associated withan incentive (e.g., discount, etc.). In some examples, the subscriptionmodule 112 can wait to send such an offer until a prescribed period oftime has lapsed, until transaction data identifies another subscriptionopportunity, etc.

FIG. 14 illustrates an example process 1400 for determining pricing fora subscription as described herein.

Block 1402 illustrates receiving an indication of a price range forwhich a merchant agrees to offer a subscription. In some examples, amerchant can provide a price range for which the merchant agrees tooffer a subscription and/or items associated with the subscription.

Block 1404 illustrates offering the subscription for different priceswithin the price range. In at least one example, the subscription module112 can offer a subscription for an item to one or more customers,wherein individual of the customers are offered the subscription fordifferent prices within the price range. That is, in at least oneexample, the subscription module 112 can utilize AB testing to optimizepricing or discounts for the subscription and/or items associatedtherewith.

Block 1406 illustrates determining subscription data based at least inpart on subscriptions purchased at the different prices. In at least oneexample, the subscription module 112 can monitor subscriptionspurchased, for example, over a period of time. The subscription module112 can generate subscription data which can indicate conversion rates,sales rates, cancellation rates, etc. associated with subscriptionsoffered at the different prices, over a period of time.

Block 1408 illustrates determining a price of the subscription based atleast in part on the subscription data. In at least one example, thesubscription module 112 can determine a price for the subscription basedat least in part on the subscription data. For example, if one of theprices is associated with a conversion rate that is higher than theother prices within the range, the subscription module 112 can recommendthe merchant offer the subscription at the price associated with thehighest conversion rate. Additionally or alternatively, if one of theprices is associated with a sales rate that is higher than the otherprices within the range, the subscription module 112 can recommend themerchant offer the subscription at the price associated with the highestsales rate. Moreover, if one of the prices is associated with acancellation rate that is lower than the other prices within the range,the subscription module 112 can recommend the merchant offer thesubscription at the price associated with the lowest cancellation rate.

In at least one example, the subscription module 112 can continuouslyoptimize pricing and/or discounts based on techniques described withrespect to process 1400.

Furthermore, in at least one example, the subscription module 112 canadditionally or alternatively perform similar testing to determine aprice for a subscription that is likely to generate particular marginsfor the merchant. For instance, a merchant can provide a target marginassociated with a subscription and the subscription module 112 can offerthe subscription at different prices (e.g., via AB testing) to determinehow such pricing affect the target margin. That is, the subscriptionmodule can leverage the results to find the best price for the merchant(e.g., for achieving the target margin) and can continuously optimizethe price offered to new customers.

FIG. 15 illustrates an example environment 1500. The environment 1500includes server computing device(s) 1502 that can communicate over anetwork 1504 with user devices 1506 (which, in some examples can bemerchant devices 1508 (individually, 1508(A)-1508(N))) and/or servercomputing device(s) 1510 associated with third-party serviceprovider(s). The server computing device(s) 1502 can be associated witha service provider 1512 that can provide one or more services for thebenefit of users 1514, as described below. Actions attributed to theservice provider 1512 can be performed by the server computing device(s)1502. Similarly, actions attributed to users can be performed by and/orvia the user device(s) 1506, as described herein.

In at least one example, the server(s) 102 described above withreference to FIG. 1 corresponds to the server(s) 1502 described herein.Further, the user devices 1506 can correspond to the merchant device(s)104 and/or customer device(s) 106 described above with reference toFIG. 1. In at least one example, the users 514 can correspond to themerchant(s) 108 and/or customer(s) 110 described above with reference toFIG. 1. The network(s) 1504 can correspond to the network(s) 107described above with reference to FIG. 1. That is, the exampleenvironment 1500 can perform techniques for, among other things asdescribed below, intelligently identifying opportunities forsubscriptions for merchants and/or customers using transaction dataassociated with past transactions, as described above.

As described above, a subscription is an arrangement for providing,receiving, or making use of something of a continuing or periodicnature. Rather than selling items (e.g., goods or services)individually, many merchants offer customers subscriptions wherecustomers pay a recurring price at regular intervals for access to agood or a service. However, in conventional technologies, merchants optto offer only certain items via a subscription model, e.g., based onitem availability or knowledge that items are consumable (and thusrequire replacement). Many conventional technologies require merchantsto create a subscription plan. That is, conventional technologies areinefficient and cause friction for merchants. Many items that are ripefor subscriptions are overlooked and merchants don't take the time tocreate subscription plans because of the time and resources required.

Conventional technologies do not have access to transaction data asdescribed herein. That is, conventional technologies do not utilize anetwork-based merchant environment, as illustrated in FIG. 15, togenerate and/or access transaction data for multiple, differentmerchants (and customers) for determining buying patterns acrossmultiple, different merchants (and customers). Such buying patterns canbe used to intelligently identify subscription opportunities formerchants and/or customers, even for items that are otherwise notidentified by a traditional subscription model. That is, the exampleenvironment 1500 illustrated in FIG. 15, can leverage transactiondata—that can include item-level granularity—associated with multiple,different merchants (and/or customers) to generate customized and/orpersonalized subscription opportunities as opposed to theone-size-fits-all subscriptions that are availed via conventionaltechnologies. For instance, techniques described herein can identifysubscription opportunities that enable customers to receive items at afrequency particular to their buying habits (or other customers similarto the customers) and/or enable merchants to provide items at afrequency that is observed from buying habits of their customers and/orcustomers of other or similar merchants. In some implementations,creating customer-specific subscription flows can simplify networkcomplexities and improve network efficiencies by replacingone-off/irregular purchase behavior with predictable purchase behavior.

Techniques described herein offer various benefits to entitiesassociated with the network-based merchant environment, as illustratedin FIG. 15. For instance, by providing a recommendation to a merchantbased on customer purchase behavior, the merchant is more likely toconvert a customer into a repeat customer or even a subscriber. As such,the merchant can receive an incremental increase in revenue based onensuring that a customer purchases an item repeatedly as opposed torunning the risk of the customer forgetting to make their regularpurchase. Furthermore, more subscriptions enable recurring revenue andincreased cash flow for merchants. Moreover, techniques described hereinenable merchants to dynamically offer subscriptions on the fly based onwhat their customers are purchasing, thereby reducing the friction ofgenerating and/or managing subscriptions. For customers, techniquesdescribed herein reduce friction associated with regular purchases and,in some examples, enable customers to subscribe to items or servicesthrough subscriptions that are customized and/or personalized for them.Additional benefits and efficiencies are described throughout thisdisclosure.

The environment 1500 can include a plurality of user devices 1506, asdescribed above. Each one of the plurality of user devices 1506 can beany type of computing device such as a tablet computing device, a smartphone or mobile communication device, a laptop, a netbook or otherportable computer or semi-portable computer, a desktop computing device,a terminal computing device or other semi-stationary or stationarycomputing device, a dedicated device, a wearable computing device orother body-mounted computing device, an augmented reality device, avirtual reality device, an Internet of Things (IoT) device, etc. In someexamples, individual ones of the user devices can be operable by users1514. The users 1514 can be referred to as customers, buyers, merchants,sellers, borrowers, employees, employers, payors, payees, couriers andso on. The users 1514 can interact with the user devices 1506 via userinterfaces presented via the user devices 1506. In at least one example,a user interface can be presented via a web browser, or the like. Inother examples, a user interface can be presented via an application,such as a mobile application or desktop application, which can beprovided by the service provider 1512 or which can be an otherwisededicated application. In some examples, individual of the user devices1506 can have an instance or versioned instance of an application, whichcan be downloaded from an application store, for example, which canpresent the user interface(s) described herein. In at least one example,a user 1514 can interact with the user interface via touch input, spokeninput, or any other type of input.

As described above, in at least one example, the users 1514 can includemerchants 1516 (individually, 1516(A)-1516(N)). In an example, themerchants 1516 can operate respective merchant devices 1508, which canbe user devices 1506 configured for use by merchants 1516. For thepurpose of this discussion, a “merchant” can be any entity that offersitems (e.g., goods or services) for purchase or other means ofacquisition (e.g., rent, borrow, barter, etc.). The merchants 1516 canoffer items for purchase or other means of acquisition viabrick-and-mortar stores, mobile stores (e.g., pop-up shops, food trucks,etc.), online stores, combinations of the foregoing, and so forth. Insome examples, at least some of the merchants 1516 can be associatedwith a same entity but can have different merchant locations and/or canhave franchise/franchisee relationships. In additional or alternativeexamples, the merchants 1516 can be different merchants. That is, in atleast one example, the merchant 1516(A) is a different merchant than themerchant 1516(B) and/or the merchant 1516(C).

For the purpose of this discussion, “different merchants” can refer totwo or more unrelated merchants. “Different merchants” therefore canrefer to two or more merchants that are different legal entities (e.g.,natural persons and/or corporate persons) that do not share accounting,employees, branding, etc. “Different merchants,” as used herein, havedifferent names, employer identification numbers (EIN)s, lines ofbusiness (in some examples), inventories (or at least portions thereof),and/or the like. Thus, the use of the term “different merchants” doesnot refer to a merchant with various merchant locations orfranchise/franchisee relationships. Such merchants—with various merchantlocations or franchise/franchisee relationships—can be referred to asmerchants having different merchant locations and/or different commercechannels.

Each merchant device 1508 can have an instance of a POS application 1518stored thereon. The POS application 1518 can configure the merchantdevice 1508 as a POS terminal, which enables the merchant 1516(A) tointeract with one or more customers 1520. As described above, the users1514 can include customers, such as the customers 1520 shown asinteracting with the merchant 1516(A). For the purpose of thisdiscussion, a “customer” can be any entity that acquires items frommerchants. While only two customers 1520 are illustrated in FIG. 15, anynumber of customers 1520 can interact with the merchants 1516. Further,while FIG. 15 illustrates the customers 1520 interacting with themerchant 1516(A), the customers 1520 can interact with any of themerchants 1516.

In at least one example, interactions between the customers 1520 and themerchants 1516 that involve the exchange of funds (from the customers1520) for items (from the merchants 1516) can be referred to as “POStransactions” and/or “transactions.” In at least one example, the POSapplication 1518 can determine transaction data associated with the POStransactions. Transaction data can include payment information, whichcan be obtained from a reader device 1522 associated with the merchantdevice 1508(A), user authentication data, purchase amount information,point-of-purchase information (e.g., item(s) purchased, date ofpurchase, time of purchase, etc.), etc. The POS application 1518 cansend transaction data to the server computing device(s) 1502.Furthermore, the POS application 1518 can present a UI to enable themerchant 1516(A) to interact with the POS application 1518 and/or theservice provider 1512 via the POS application 1518.

In at least one example, the merchant device 1508(A) can be aspecial-purpose computing device configured as a POS terminal (via theexecution of the POS application 1518). In at least one example, the POSterminal may be connected to a reader device 1522, which is capable ofaccepting a variety of payment instruments, such as credit cards, debitcards, gift cards, short-range communication-based payment instruments,and the like, as described below. In at least one example, the readerdevice 1522 can plug in to a port in the merchant device 1508(A), suchas a microphone port, a headphone port, an audio-jack, a data port, orother suitable port. In additional or alternative examples, the readerdevice 1522 can be coupled to the merchant device 1508(A) via anotherwired or wireless connection, such as via a Bluetooth®, BLE, and so on.Additional details are described below with reference to FIG. 16. Insome examples, the reader device 1522 can read information fromalternative payment instruments including, but not limited to,wristbands and the like.

In some examples, the reader device 1522 may physically interact withpayment instruments such as magnetic stripe payment cards, EMV paymentcards, and/or short-range communication (e.g., near field communication(NFC), radio frequency identification (RFID), Bluetooth®, Bluetooth® lowenergy (BLE), etc.) payment instruments (e.g., cards or devicesconfigured for tapping). The POS terminal may provide a rich userinterface, communicate with the reader device 1522, and communicate withthe server computing device(s) 1502, which can provide, among otherservices, a payment processing service. The server computing device(s)1502 associated with the service provider 1512 can communicate withserver computing device(s) 1510, as described below. In this manner, thePOS terminal and reader device 1522 may collectively processtransaction(s) between the merchants 1516 and customers 1520. In someexamples, POS terminals and reader devices can be configured inone-to-one pairings. In other examples, the POS terminals and readerdevices can be configured in many-to-one pairings (e.g., one POSterminal coupled to multiple reader devices or multiple POS terminalscoupled to one reader device). In some examples, there could be multiplePOS terminal(s) connected to a number of other devices, such as“secondary” terminals, e.g., back-of-the-house systems, printers,line-buster devices, POS readers, and the like, to allow for informationfrom the secondary terminal to be shared between the primary POSterminal(s) and secondary terminal(s), for example via short-rangecommunication technology. This kind of arrangement may also work in anoffline-online scenario to allow one device (e.g., secondary terminal)to continue taking user input, and synchronize data with another device(e.g., primary terminal) when the primary or secondary terminal switchesto online mode. In other examples, such data synchronization may happenperiodically or at randomly selected time intervals.

While, the POS terminal and the reader device 1522 of the POS system1524 are shown as separate devices, in additional or alternativeexamples, the POS terminal and the reader device 1522 can be part of asingle device. In some examples, the reader device 1522 can have adisplay integrated therein for presenting information to the customers1520. In additional or alternative examples, the POS terminal can have adisplay integrated therein for presenting information to the customers1520. POS systems, such as the POS system 1524, may be mobile, such thatPOS terminals and reader devices may process transactions in disparatelocations across the world. POS systems can be used for processingcard-present transactions and card-not-present (CNP) transactions, asdescribed below.

A card-present transaction is a transaction where both a customer 1520and his or her payment instrument are physically present at the time ofthe transaction. Card-present transactions may be processed by swipes,dips, taps, or any other interaction between a physical paymentinstrument (e.g., a card), or otherwise present payment instrument, anda reader device 1522 whereby the reader device 1522 is able to obtainpayment data from the payment instrument. A swipe is a card-presenttransaction where a customer 1520 slides a card, or other paymentinstrument, having a magnetic strip through a reader device 1522 thatcaptures payment data contained in the magnetic strip. A dip is acard-present transaction where a customer 1520 inserts a paymentinstrument having an embedded microchip (i.e., chip) into a readerdevice 1522 first. The dipped payment instrument remains in the paymentreader until the reader device 1522 prompts the customer 1520 to removethe card, or other payment instrument. While the payment instrument isin the reader device 1522, the microchip can create a one-time codewhich is sent from the POS system 1524 to the server computing device(s)1510 (which can be associated with third-party service providers thatprovide payment services, including but not limited to, an acquirerbank, an issuer, and/or a card payment network (e.g., Mastercard®,VISA®, etc.)) to be matched with an identical one-time code. A tap is acard-present transaction where a customer 1520 may tap or hover his orher payment instrument (e.g., card, electronic device such as a smartphone running a payment application, etc.) over a reader device 1522 tocomplete a transaction via short-range communication (e.g., NFC, RFID,Bluetooth®, BLE, etc.). Short-range communication enables the paymentinstrument to exchange information with the reader device 1522. A tapmay also be called a contactless payment.

A CNP transaction is a transaction where a card, or other paymentinstrument, is not physically present at the POS such that payment datais required to be manually keyed in (e.g., by a merchant, customer,etc.), or payment data is required to be recalled from a card-on-filedata store, to complete the transaction.

The POS system 1524, the server computing device(s) 1502, and/or theserver computing device(s) 1510 may exchange payment information andtransaction data to determine whether transactions are authorized. Forexample, the POS system 1524 may provide encrypted payment data, userauthentication data, purchase amount information, point-of-purchaseinformation, etc. (collectively, transaction data) to server computingdevice(s) 1502 over the network(s) 1504. Such information can beassociated with the transaction data 120 described above with referenceto FIG. 1. The server computing device(s) 1502 may send the transactiondata to the server computing device(s) 1510. As described above, in atleast one example, the server computing device(s) 1510 can be associatedwith third-party service providers that provide payment services,including but not limited to, an acquirer bank, an issuer, and/or a cardpayment network (e.g., Mastercard®, VISA®, etc.)

For the purpose of this discussion, the “payment service providers” canbe acquiring banks (“acquirer”), issuing banks (“issuer”), card paymentnetworks, and the like. In an example, an acquirer is a bank orfinancial institution that processes payments (e.g., credit or debitcard payments) and can assume risk on behalf of merchants(s). Anacquirer can be a registered member of a card association (e.g., Visa®,MasterCard®), and can be part of a card payment network. The acquirer(e.g., the server computing device(s) 1510 associated therewith) cansend a fund transfer request to a server computing device of a cardpayment network (e.g., Mastercard®, VISA®, etc.) to determine whetherthe transaction is authorized or deficient. In at least one example, theservice provider 1512 can serve as an acquirer and connect directly withthe card payment network.

The card payment network (e.g., the server computing device(s) 1510associated therewith) can forward the fund transfer request to anissuing bank (e.g., “issuer”). The issuer is a bank or financialinstitution that offers a financial account (e.g., credit or debit cardaccount) to a user. An issuer can issue payment cards to users and canpay acquirers for purchases made by cardholders to which the issuingbank has issued a payment card. The issuer (e.g., the server computingdevice(s) 1510 associated therewith) can make a determination as towhether the customer has the capacity to absorb the relevant chargeassociated with the payment transaction. In at least one example, theservice provider 1512 can serve as an issuer and/or can partner with anissuer. The transaction is either approved or rejected by the issuerand/or the card payment network (e.g., the server computing device(s)1510 associated therewith), and a payment authorization message iscommunicated from the issuer to the POS device via a path opposite ofthat described above, or via an alternate path.

As described above, the server computing device(s) 1510, which can beassociated with payment service provider(s), may determine whether thetransaction is authorized based on the transaction data, as well asinformation relating to parties to the transaction (e.g., the customer1520 and/or the merchant 1516(A)). In at least one example, such atransaction can be associated with a subscription and/or an installmentof a subscription (e.g., an order associated therewith). The servercomputing device(s) 1510 may send an authorization notification over thenetwork(s) 1504 to the server computing device(s) 1502, which may sendthe authorization notification to the POS system 1524 over thenetwork(s) 1504 to indicate whether the transaction is authorized. Theserver computing device(s) 1502 may also transmit additional informationsuch as transaction identifiers to the POS system 1524. In one example,the server computing device(s) 1502 may include a merchant applicationand/or other functional components for communicating with the POS system1524 and/or the server computing device(s) 1510 to authorize or declinetransactions.

Based on the authentication notification that is received by the POSsystem 1524 from server computing device(s) 1502, the merchant 1516(A)may indicate to the customer 1520 whether the transaction has beenapproved. In some examples, approval may be indicated at the POS system1524, for example, at a display of the POS system 1524. In otherexamples, such as with a smart phone or watch operating as a short-rangecommunication payment instrument, information about the approvedtransaction may be provided to the short-range communication paymentinstrument for presentation via a display of the smart phone or watch.In some examples, additional or alternative information can additionallybe presented with the approved transaction notification including, butnot limited to, receipts, special offers, coupons, or loyalty programinformation.

As mentioned above, the service provider 1512 can provide, among otherservices, payment processing services, inventory management services,catalog management services, business banking services, financingservices, lending services, reservation management services,web-development services, payroll services, employee managementservices, appointment services, loyalty tracking services, restaurantmanagement services, order management services, fulfillment services,peer-to-peer payment services, onboarding services, identityverification (IDV) services, and so on. In some examples, the users 1514can access all of the services of the service provider 1512. In otherexamples, the users 1514 can have gradated access to the services, whichcan be based on risk tolerance, IDV outputs, subscriptions, and so on.In at least one example, access to such services can be availed to themerchants 1516 via the POS application 1518. In additional oralternative examples, each service can be associated with its own accesspoint (e.g., application, web browser, etc.).

The service provider 1512 can offer payment processing services forprocessing payments on behalf of the merchants 1516, as described above.For example, the service provider 1512 can provision payment processingsoftware, payment processing hardware and/or payment processing servicesto merchants 1516, as described above, to enable the merchants 1516 toreceive payments from the customers 1520 when conducting POStransactions with the customers 1520. For instance, the service provider1512 can enable the merchants 1516 to receive cash payments, paymentcard payments, and/or electronic payments from customers 1520 for POStransactions and the service provider 1512 can process transactions onbehalf of the merchants 1516.

As the service provider 1512 processes transactions on behalf of themerchants 1516, the service provider 1512 can maintain accounts orbalances for the merchants 1516 in one or more ledgers. For example, theservice provider 1512 can analyze transaction data received for atransaction to determine an amount of funds owed to a merchant 1516(A)for the transaction. In at least one example, such an amount can be atotal purchase price less fees charged by the service provider 1512 forproviding the payment processing services. Based on determining theamount of funds owed to the merchant 1516(A), the service provider 1512can deposit funds into an account of the merchant 1516(A). The accountcan have a stored balance, which can be managed by the service provider1512. The account can be different from a conventional bank account atleast because the stored balance is managed by a ledger of the serviceprovider 1512 and the associated funds are accessible via variouswithdrawal channels including, but not limited to, scheduled deposit,same-day deposit, instant deposit, and a linked payment instrument.

A scheduled deposit can occur when the service provider 1512 transfersfunds associated with a stored balance of the merchant 1516(A) to a bankaccount of the merchant 1516(A) that is held at a bank or otherfinancial institution (e.g., associated with the server computingdevice(s) 1510). Scheduled deposits can occur at a prearranged timeafter a POS transaction is funded, which can be a business day after thePOS transaction occurred, or sooner or later. In some examples, themerchant 1516(A) can access funds prior to a scheduled deposit. Forinstance, the merchant 1516(A) may have access to same-day deposits(e.g., wherein the service provider 1512 deposits funds from the storedbalance to a linked bank account of the merchant on a same day as POStransaction, in some examples prior to the POS transaction being funded)or instant deposits (e.g., wherein the service provider 1512 depositsfunds from the stored balance to a linked bank account of the merchanton demand, such as responsive to a request). Further, in at least oneexample, the merchant 1516(A) can have a payment instrument that islinked to the stored balance that enables the merchant to access thefunds without first transferring the funds from the account managed bythe service provider 1512 to the bank account of the merchant 1516(A).

In at least one example, the service provider 1512 may provide inventorymanagement services. That is, the service provider 1512 may provideinventory tracking and reporting. Inventory management services mayenable the merchant 1516(A) to access and manage a database storing dataassociated with a quantity of each item that the merchant 1516(A) hasavailable (i.e., an inventory). Furthermore, in at least one example,the service provider 1512 can provide catalog management services toenable the merchant 1516(A) to maintain a catalog, which can be adatabase storing data associated with items that the merchant 1516(A)has available for acquisition (i.e., catalog management services). In atleast one example, the catalog may include a plurality of data items anda data item of the plurality of data items may represent an item thatthe merchant 1561(A) has available for acquisition. The service provider1512 can offer recommendations related to pricing of the items,placement of items on the catalog, and multi-party fulfilment of theinventory.

In at least one example, the service provider 1512 can provide businessbanking services, which allow the merchant 1516(A) to track deposits(from payment processing and/or other sources of funds) into an accountof the merchant 1516(A), payroll payments from the account (e.g.,payments to employees of the merchant 1516(A)), payments to othermerchants (e.g., business-to-business) directly from the account or froma linked debit card, withdrawals made via scheduled deposit and/orinstant deposit, etc. Furthermore, the business banking services canenable the merchant 1516(A) to obtain a customized payment instrument(e.g., credit card), check how much money they are earning (e.g., viapresentation of available earned balance), understand where their moneyis going (e.g., via deposit reports (which can include a breakdown offees), spend reports, etc.), access/use earned money (e.g., viascheduled deposit, instant deposit, linked payment instrument, etc.),feel in control of their money (e.g., via management of depositschedule, deposit speed, linked instruments, etc.), etc. Moreover, thebusiness banking services can enable the merchants 1516 to visualizetheir cash flow to track their financial health, set aside money forupcoming obligations (e.g., savings), organize money around goals, etc.

In at least one example, the service provider 1512 can provide financingservices and products, such as via business loans, consumer loans, fixedterm loans, flexible term loans, and the like. In at least one example,the service provider 1512 can utilize one or more risk signals todetermine whether to extend financing offers and/or terms associatedwith such financing offers.

In at least one example, the service provider 1512 can provide financingservices for offering and/or lending a loan to a borrower that is to beused for, in some instances, financing the borrower's short-termoperational needs (e.g., a capital loan). For instance, a potentialborrower that is a merchant can obtain a capital loan via a capital loanproduct in order to finance various operational costs (e.g., rent,payroll, inventory, etc.). In at least one example, the service provider1512 can offer different types of capital loan products. For instance,in at least one example, the service provider 1512 can offer a dailyrepayment loan product, wherein a capital loan is repaid daily, forinstance, from a portion of transactions processed by the paymentprocessing service on behalf of the borrower. Additionally and/oralternatively, the service provider 1512 can offer a monthly repaymentloan product, wherein a capital loan is repaid monthly, for instance,via a debit from a bank account linked to the payment processingservice. The credit risk of the merchant may be evaluated using riskmodels that take into account factors, such as payment volume, creditrisk of similarly situated merchants, past transaction history,seasonality, credit history, and so on.

Additionally or alternatively, the service provider 1512 can providefinancing services for offering and/or lending a loan to a borrower thatis to be used for, in some instances, financing the borrower's consumerpurchase (e.g., a consumer loan). In at least one example, a borrowercan submit a request for a loan to enable the borrower to purchase anitem from a merchant, which can be one of the merchants 1516. Theservice provider 1512 can generate the loan based at least in part ondetermining that the borrower purchased or intends to purchase the itemfrom the merchant. The loan can be associated with a balance based on anactual purchase price of the item and the borrower can repay the loanover time. In some examples, the borrower can repay the loan viainstallments, which can be paid via funds managed and/or maintained bythe service provider 1512 (e.g., from payments owed to the merchant frompayments processed on behalf of the merchant, funds transferred to themerchant, etc.). The service provider 1512 can offer specific financialproducts, such as payment instruments, tied specifically to the loanproducts. For example, in one implementation, the server provider 1512associates capital to a merchant or customer's debit card, where the useof the debit card is defined by the terms of the loan. In some examples,the merchant may only use the debit card for making specific purchases.In other examples, the “installment” associated with the loan product iscredited directly via the payment instrument. The payment instrument isthus customized to the loan and/or the parties associated with the loan.

The service provider 1512 can provide web-development services, whichenable users 1514 who are unfamiliar with HTML, XML, JavaScript, CSS, orother web design tools to create and maintain professional andaesthetically pleasing websites. Some of these web page editingapplications allow users to build a web page and/or modify a web page(e.g., change, add, or remove content associated with a web page).Further, in addition to websites, the web-development services cancreate and maintain other online omni-channel presences, such as socialmedia posts for example. In some examples, the resulting web page(s)and/or other content items can be used for offering item(s) for sale viaan online/e-commerce platform. That is, the resulting web page(s) and/orother content items can be associated with an online store or offeringby the one or more of the merchants 1516. In at least one example, theservice provider 1512 can recommend and/or generate content items tosupplement omni-channel presences of the merchants 1516. That is, if amerchant of the merchants 1516 has a web page, the service provider1512—via the web-development or other services—can recommend and/orgenerate additional content items to be presented via other channel(s),such as social media, email, etc.

Furthermore, the service provider 1512 can provide payroll services toenable employers to pay employees for work performed on behalf ofemployers. In at least one example, the service provider 1512 canreceive data that includes time worked by an employee (e.g., throughimported timecards and/or POS interactions), sales made by the employee,gratuities received by the employee, and so forth. Based on such data,the service provider 1512 can make payroll payments to employee(s) onbehalf of an employer via the payroll service. For instance, the serviceprovider 1512 can facilitate the transfer of a total amount to be paidout for the payroll of an employee from the bank of the employer to thebank of the service provider 1512 to be used to make payroll payments.In at least one example, when the funds have been received at the bankof the service provider 1512, the service provider 1512 can pay theemployee, such as by check or direct deposit, often a day, a week, ormore after when the work was actually performed by the employee. Inadditional or alternative examples, the service provider 1512 can enableemployee(s) to receive payments via same-day or instant deposit based atleast in part on risk and/or reliability analyses performed by theservice provider 1512.

Moreover, in at least one example, the service provider 1512 can provideemployee management services for managing schedules of employees.Further, the service provider 1512 can provide appointment services forenabling users 1514 to set schedules for scheduling appointments and/orusers 1514 to schedule appointments.

In some examples, the service provider 1512 can provide restaurantmanagement services to enable users 1514 to make and/or managereservations, to monitor front-of-house and/or back-of-house operations,and so on. In such examples, the merchant device(s) 1508 and/or servercomputing device(s) 1502 can be configured to communicate with one ormore other computing devices, which can be located in the front-of-house(e.g., POS device(s)) and/or back-of-house (e.g., kitchen displaysystem(s) (KDS)). In at least one example, the service provider 1512 canprovide order management services and/or fulfillment services to enablerestaurants to manage open tickets, split tickets, and so on and/ormanage fulfillment services. In some examples, such services can beassociated with restaurant merchants, as described above. In additionalor alternative examples, such services can be any type of merchant.

In at least one example, the service provider 1512 can providefulfilment services, which can use couriers for delivery, whereincouriers can travel between multiple locations to provide deliveryservices, photography services, etc. Couriers can be users 1514 who cantravel between locations to perform services for a requesting user 1514(e.g., deliver items, capture images, etc.). In some examples, thecourier can receive compensation from the service provider 1512. Thecourier can employ one or more vehicles, such as automobiles, bicycles,scooters, motorcycles, buses, airplanes, helicopters, boats,skateboards, etc. Although, in other instances the courier can travel byfoot or otherwise without a vehicle. Some examples discussed hereinenable people to participate as couriers in a type of crowdsourcedservice economy. Here, essentially any person with a mobile device isable to immediately become a courier, or cease to be a courier, in acourier network that provides services as described herein. In at leastone example, the couriers can be unmanned aerial vehicles (e.g.,drones), autonomous vehicles, or any other type of vehicle capable ofreceiving instructions for traveling between locations. In someexamples, the service provider 1512 can receive requests for courierservices, automatically assign the requests to active couriers, andcommunicate dispatch instructions to couriers via user interface (e.g.,application, web browser, or other access point) presented viarespective devices 1506.

In some examples, the service provider 1512 can provide omni-channelfulfillment services. For instance, if a customer places an order with amerchant and the merchant cannot fulfill the order because one or moreitems are out of stock or otherwise unavailable, the service provider1512 can leverage other merchants and/or sales channels that are part ofthe platform of the service provider 1512 to fulfill the customer'sorder. That is, another merchant can provide the one or more items tofulfill the order of the customer. Furthermore, in some examples,another sales channel (e.g., online, brick-and-mortar, etc.) can be usedto fulfill the order of the customer.

In some examples, the service provider 1512 can enable conversationalcommerce via conversational commerce services, which can use one or moremachine learning mechanisms to analyze messages exchanged between two ormore users 1514, voice inputs into a virtual assistant or the like, todetermine intents of user(s) 1514. In some examples, the serviceprovider 1512 can utilize determined intents to automate customerservice, offer promotions, provide recommendations, or otherwiseinteract with customers in real-time. In at least one example, theservice provider 1512 can integrate products and services, and paymentmechanisms into a communication platform (e.g., messaging, etc.) toenable customers to make purchases, or otherwise transact, withouthaving to call, email, or visit a web page or other channel of amerchant. That is, conversational commerce alleviates the need forcustomers to toggle back and forth between conversations and web pagesto gather information and make purchases.

In at least one example, the service provider 1512 can provide apeer-to-peer payment service that enables peer-to-peer payments betweentwo or more users 1514. In at least one example, the service provider1512 can communicate with instances of a payment application (or otheraccess point) installed on devices 1506 configured for operation byusers 1514. In an example, an instance of the payment applicationexecuting on a first device operated by a payor can send a request tothe service provider 1512 to transfer an amount of funds (e.g., fiatcurrency or non-fiat currency such as cryptocurrency, securities, andrelated assets) from an account of the payor to an account of a payee(e.g., a peer-to-peer payment). The service provider 1512 can facilitatethe transfer and can send a notification to an instance of the paymentapplication executing on a second mobile device operated by the payeethat the transfer is in process (or has been completed). In someexamples, the service provider 1512 can send additional or alternativeinformation to the instances of the payment application (e.g., lowbalance to the payor, current balance to the payor or the payee, etc.).In some implementations, the payor and/or payee can be identifiedautomatically, e.g., based on context, proximity, prior transactionhistory, and so on. In other examples, the payee can send a request forfunds to the payor prior to the payor initiating the transfer of funds.The funds transferred can be associated with any digital currency type,including, but not limited to, cash, cryptocurrency, etc. In someembodiments, the service provider 1512 funds the request to payee onbehalf of the payor, to speed up the transfer process and compensate forany lags that may be attributed to payor's financial network.

In some implementations, the service provider 1512 can trigger thepeer-to-peer payment process through identification of a “payment proxy”having a particular syntax. For example, the syntax includes a monetarycurrency indicator prefixing one or more alphanumeric characters (e.g.,$Cash). The currency indicator operates as the tagging mechanism thatindicates to a computer system to treat the inputs as a request from thesender to transfer cash, where detection of the syntax (which includesone or more alphanumeric characters tagged by a monetary currencyindicator) triggers a transfer of cash. The currency indicator cancorrespond to various currencies including but not limited to, dollar($), euro (€), pound (£), rupee (

), yuan (¥), etc. Although use of the dollar currency indicator ($) isused herein, it is to be understood that any currency symbol couldequally be used. The peer-to-peer process can be initiated through aparticular application executing on the user devices 1506.

In some embodiments, the peer-to-peer process can be implemented withina forum context. The term “forum,” as used here, refers to a contentprovider's media channel (e.g., a social networking platform, amicroblog, a blog, video sharing platform, a music sharing platform,etc.) that enables user interaction and engagement through comments,posts, messages on electronic bulletin boards, messages on a socialnetworking platform, and/or any other types of messages. The forum canbe employed by a content provider to enable users of the forum tointeract with one another, (e.g., through creating messages, postingcomments, etc.). In some embodiments, “forum” may also refer to anapplication or webpage of an e-commerce or retail organization thatoffers products and/or services. Such websites can provide an online“form” to complete before or after the products or services are added toa virtual cart. The online form may include one or more fields toreceive user interaction and engagement. Examples include name and otheridentification of the user, shipping address of the user, etc. Some ofthese fields may be configured to receive payment information, such as apayment proxy, in lieu of other kinds of payment mechanisms, such ascredit cards, debit cards, prepaid cards, gift cards, virtual wallets,etc.

In some embodiments, the peer-to-peer process can be implemented withina communication application context, such as a messaging applicationcontext. The term “messaging application,” as used here, refers to anymessaging application that enables communication between users (e.g.,sender and recipient of a message) over a wired or wirelesscommunications network, through use of a communication message. Themessaging application can be employed by the service provider 1512. Forinstance, the service provider 1512 can offer messaging services thatprovides a communication service to users via a messaging application(e.g., chat or messaging capability). The messaging application caninclude, for example, a text messaging application for communicationbetween phones (e.g., conventional mobile telephones or smartphones), ora cross-platform instant messaging application for smartphones andphones that use the Internet for communication. The messagingapplication can be executed on a user device 1506 (e.g., mobile deviceor conventional personal computer (PC)) based on instructionstransmitted to and from the server computing device(s) 1502 (which, insuch an example can be called a “messaging server”). In some instances,the messaging application can include a payment application withmessaging capability that enables users of the payment application tocommunicate with one another. In such instances, the payment applicationcan be executed on a user device 1506 based on instructions transmittedto and from the server computing device(s) 1502 (e.g., the paymentservice discussed in this description or another payment service thatsupports payment transactions).

In at least some embodiments, the peer-to-peer process can beimplemented within a landing page context. The term “landing page,” asused here, refers to a virtual location identified by a personalizedlocation address that is dedicated to collect payments on behalf of arecipient associated with the personalized location address. Thepersonalized location address that identifies the landing page caninclude a payment proxy discussed above. The service provider 1512 cangenerate the landing page to enable the recipient to convenientlyreceive one or more payments from one or more senders. In someembodiments, the personalized location address identifying the landingpage is a uniform resource locator (URL) that incorporates the paymentproxy. In such embodiments, the landing page is a web page, e.g.,www.cash.me/$Cash.

In at least one example, a user 1514 may be new to the service provider1512 such that the user 1514 that has not registered (e.g., subscribedto receive access to one or more services offered by the serviceprovider) with the service provider 1512. The service provider 1512 canoffer onboarding services for registering a potential user 1514 with theservice provider 1512. In some examples, onboarding can involvepresenting various questions, prompts, and the like to a potential user1514 to obtain information that can be used to generate a profile forthe potential user 1514. In at least one example, the service provider1512 can provide limited or short-term access to its services prior to,or during, onboarding (e.g., a user of a peer-to-peer payment servicecan transfer and/or receive funds prior to being fully onboarded, amerchant can process payments prior to being fully onboarded, etc.). Inat least one example, responsive to the potential user 1514 providingall necessary information, the potential user 1514 can be onboarded tothe service provider 1512. In such an example, any limited or short-termaccess to services of the service provider 1512 can be transitioned tomore permissive (e.g., less limited) or longer-term access to suchservices.

The service provider 1512 can be associated with IDV services, which canbe used by the service provider 1512 for compliance purposes and/or canbe offered as a service, for instance to third-party service providers(e.g., associated with the server computing device(s) 1510). That is,the service provider 1512 can offer IDV services to verify the identityof users 1514 seeking to use or using their services. Identityverification requires a customer (or potential customer) to provideinformation that is used by compliance departments to prove that theinformation is associated with an identity of a real person or entity.In at least one example, the service provider 1512 can perform servicesfor determining whether identifying information provided by a user 1514accurately identifies the customer (or potential customer) (i.e., Is thecustomer who they say they are?).

The service provider 1512 is capable of providing additional oralternative services and the services described above are offered as asampling of services. In at least one example, the service provider 1512can exchange data with the server computing device(s) 1510 associatedwith third-party service providers. Such third-party service providerscan provide information that enables the service provider 1512 toprovide services, such as those described above. In additional oralternative examples, such third-party service providers can accessservices of the service provider 1512. That is, in some examples, thethird-party service providers can be subscribers, or otherwise access,services of the service provider 1512.

Techniques described herein can be configured to operate in bothreal-time/online and offline modes. “Online” modes refer to modes whendevices are capable of communicating with the service provider 1512(e.g., the server computing device(s) 1502) and/or the server computingdevice(s) 1510 via the network(s) 1504. In some examples, the merchantdevice(s) 1508 are not capable of connecting with the service provider1512 (e.g., the server computing device(s) 1502) and/or the servercomputing device(s) 1510, due to a network connectivity issue, forexample. In additional or alternative examples, the server computingdevice(s) 1502 are not capable of communicating with the servercomputing device(s) 1510 due to network connectivity issue, for example.In such examples, devices may operate in “offline” mode where at leastsome payment data is stored (e.g., on the merchant device(s) 1508)and/or the server computing device(s) 1502 until connectivity isrestored and the payment data can be transmitted to the server computingdevice(s) 1502 and/or the server computing device(s) 1510 forprocessing.

In at least one example, the service provider 1512 can be associatedwith a hub, such as an order hub, an inventory hub, a fulfillment huband so on, which can enable integration with one or more additionalservice providers (e.g., associated with the additional server computingdevice(s) 1510). In some examples, such additional service providers canoffer additional or alternative services and the service provider 1512can provide an interface or other computer-readable instructions tointegrate functionality of the service provider 1512 into the one ormore additional service providers.

Techniques described herein are directed to services provided via adistributed system of user devices 1506 that are in communication withone or more server computing devices 1502 of the service provider 1512.That is, techniques described herein are directed to a specificimplementation—or, a practical application—of utilizing a distributedsystem of user devices 1506 that are in communication with one or moreserver computing devices 1502 of the service provider 1512 to perform avariety of services, as described above. The unconventionalconfiguration of the distributed system described herein enables theserver computing device(s) 1502 that are remotely-located from end-users(e.g., users 1514) to intelligently offer services based on aggregateddata associated with the end-users, such as the users 1514 (e.g., dataassociated with multiple, different merchants and/or multiple, differentbuyers), in some examples, in near-real time. Accordingly, techniquesdescribed herein are directed to a particular arrangement of elementsthat offer technical improvements over conventional techniques forperforming payment processing services and the like. For small businessowners in particular, the business environment is typically fragmentedand relies on unrelated tools and programs, making it difficult for anowner to manually consolidate and view such data. The techniquesdescribed herein constantly or periodically monitor disparate anddistinct merchant accounts, e.g., accounts within the control of theservice provider 1512, and those outside of the control of the serviceprovider 1512, to track the business standing (payables, receivables,payroll, invoices, appointments, capital, etc.) of the merchants. Thetechniques herein provide a consolidated view of a merchant's cash flow,predict needs, preemptively offer recommendations or services, such ascapital, coupons, etc., and/or enable money movement between disparateaccounts (merchant's, another merchant's, or even payment service's) ina frictionless and transparent manner.

As described herein, artificial intelligence, machine learning, and thelike can be used to dynamically make determinations, recommendations,and the like, thereby adding intelligence and context-awareness to anotherwise one-size-fits-all scheme for providing payment processingservices and/or additional or alternative services described herein. Insome implementations, the distributed system is capable of applying theintelligence derived from an existing user base to a new user, therebymaking the onboarding experience for the new user personalized andfrictionless when compared to traditional onboarding methods. Thus,techniques described herein improve existing technological processes.

As described above, various graphical user interfaces (GUIs) can bepresented to facilitate techniques described herein. Some of thetechniques described herein are directed to user interface featurespresented via GUIs to improve interaction between users 1514 and userdevices 1506. Furthermore, such features are changed dynamically basedon the profiles of the users involved interacting with the GUIs. Assuch, techniques described herein are directed to improvements tocomputing systems.

FIG. 16 depicts an illustrative block diagram illustrating a system 1600for performing techniques described herein. The system 1600 includes auser device 1602, that communicates with server computing device(s)(e.g., server(s) 1604) via network(s) 1606 (e.g., the Internet, cablenetwork(s), cellular network(s), cloud network(s), wireless network(s)(e.g., Wi-Fi) and wired network(s), as well as close-rangecommunications such as Bluetooth®, Bluetooth® low energy (BLE), and thelike). While a single user device 1602 is illustrated, in additional oralternate examples, the system 1600 can have multiple user devices, asdescribed above with reference to FIG. 15.

In at least one example, the server(s) 102 described above withreference to FIG. 1 corresponds to the server(s) 1604 described herein.Further, the user device 1602 can correspond to any one of the merchantdevice(s) 104 or customer device(s) 106 described above with referenceto FIG. 1. The network(s) 1606 can correspond to the network(s) 107described above with reference to FIG. 1. That is, the exampleenvironment 1600 can perform techniques for, among other things,intelligently identifying opportunities for subscriptions for merchantsand/or customers using transaction data associated with pasttransactions, as described above.

As described above, a subscription is an arrangement for providing,receiving, or making use of something of a continuing or periodicnature. Rather than selling items (e.g., goods or services)individually, many merchants offer customers subscriptions wherecustomers pay a recurring price at regular intervals for access to agood or a service. However, in conventional technologies, merchants optto offer only certain items via a subscription model, e.g., based onitem availability or knowledge that items are consumable (and thusrequire replacement). Many conventional technologies require merchantsto create a subscription plan. That is, conventional technologies areinefficient and cause friction for merchants. Many items that are ripefor subscriptions are overlooked and merchants don't take the time tocreate subscription plans because of the time and resources required.

Conventional technologies do not have access to transaction data asdescribed herein. That is, conventional technologies do not utilize anetwork-based merchant environment, as illustrated in FIG. 16, togenerate and/or access transaction data for multiple, differentmerchants (and customers) for determining buying patterns acrossmultiple, different merchants (and customers). Such buying patterns canbe used to intelligently identify subscription opportunities formerchants and/or customers, even for items that are otherwise notidentified by a traditional subscription model. That is, the system 1600illustrated in FIG. 16, can leverage transaction data—that can includeitem-level granularity—associated with multiple, different merchants(and/or customers) to generate customized and/or personalizedsubscription opportunities as opposed to the one-size-fits-allsubscriptions that are availed via conventional technologies. Forinstance, techniques described herein can identify subscriptionopportunities that enable customers to receive items at a frequencyparticular to their buying habits (or other customers similar to thecustomers) and/or enable merchants to provide items at a frequency thatis observed from buying habits of their customers and/or customers ofother or similar merchants. In some implementations, creatingcustomer-specific subscription flows can simplify network complexitiesand improve network efficiencies by replacing one-off/irregular purchasebehavior with predictable purchase behavior.

Techniques described herein offer various benefits availed via thesystem 1600, as illustrated in FIG. 16. For instance, by providing arecommendation to a merchant based on customer purchase behavior, themerchant is more likely to convert a customer into a repeat customer oreven a subscriber. As such, the merchant can receive an incrementalincrease in revenue based on ensuring that a customer purchases an itemrepeatedly as opposed to running the risk of the customer forgetting tomake their regular purchase. Furthermore, more subscriptions enablerecurring revenue and increased cash flow for merchants. Moreover,techniques described herein enable merchants to dynamically offersubscriptions on the fly based on what their customers are purchasing,thereby reducing the friction of generating and/or managingsubscriptions. For customers, techniques described herein reducefriction associated with regular purchases and, in some examples, enablecustomers to subscribe to items or services through subscriptions thatare customized and/or personalized for them. Additional benefits andefficiencies are described throughout this disclosure.

In at least one example, the user device 1602 can be any suitable typeof computing device, e.g., portable, semi-portable, semi-stationary, orstationary. Some examples of the user device 1602 can include, but arenot limited to, a tablet computing device, a smart phone or mobilecommunication device, a laptop, a netbook or other portable computer orsemi-portable computer, a desktop computing device, a terminal computingdevice or other semi-stationary or stationary computing device, adedicated device, a wearable computing device or other body-mountedcomputing device, an augmented reality device, a virtual reality device,an Internet of Things (IoT) device, etc. That is, the user device 1602can be any computing device capable of sending communications andperforming the functions according to the techniques described herein.The user device 1602 can include devices, e.g., payment card readers, orcomponents capable of accepting payments, as described below.

In the illustrated example, the user device 1602 includes one or moreprocessors 1608, one or more computer-readable media 1610, one or morecommunication interface(s) 1612, one or more input/output (I/O) devices1614, a display 1616, and sensor(s) 1618.

In at least one example, each processor 1608 can itself comprise one ormore processors or processing cores. For example, the processor(s) 1608can be implemented as one or more microprocessors, microcomputers,microcontrollers, digital signal processors, central processing units,state machines, logic circuitries, and/or any devices that manipulatesignals based on operational instructions. In some examples, theprocessor(s) 1608 can be one or more hardware processors and/or logiccircuits of any suitable type specifically programmed or configured toexecute the algorithms and processes described herein. The processor(s)1608 can be configured to fetch and execute computer-readableprocessor-executable instructions stored in the computer-readable media1610.

Depending on the configuration of the user device 1602, thecomputer-readable media 1610 can be an example of tangiblenon-transitory computer storage media and can include volatile andnonvolatile memory and/or removable and non-removable media implementedin any type of technology for storage of information such ascomputer-readable processor-executable instructions, data structures,program modules or other data. The computer-readable media 1610 caninclude, but is not limited to, RAM, ROM, EEPROM, flash memory,solid-state storage, magnetic disk storage, optical storage, and/orother computer-readable media technology. Further, in some examples, theuser device 1602 can access external storage, such as RAID storagesystems, storage arrays, network attached storage, storage areanetworks, cloud storage, or any other medium that can be used to storeinformation and that can be accessed by the processor(s) 1608 directlyor through another computing device or network. Accordingly, thecomputer-readable media 1610 can be computer storage media able to storeinstructions, modules or components that can be executed by theprocessor(s) 1608. Further, when mentioned, non-transitorycomputer-readable media exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

The computer-readable media 1610 can be used to store and maintain anynumber of functional components that are executable by the processor(s)1608. In some implementations, these functional components compriseinstructions or programs that are executable by the processor(s) 1608and that, when executed, implement operational logic for performing theactions and services attributed above to the user device 1602.Functional components stored in the computer-readable media 1610 caninclude a user interface 1620 to enable users to interact with the userdevice 1602, and thus the server(s) 1604 and/or other networked devices.In at least one example, the user interface 1620 can be presented via aweb browser, or the like. In other examples, the user interface 1620 canbe presented via an application, such as a mobile application or desktopapplication, which can be provided by a service provider 1512 associatedwith the server(s) 1604, or which can be an otherwise dedicatedapplication. In at least one example, a user can interact with the userinterface via touch input, spoken input, gesture, or any other type ofinput. The word “input” is also used to describe “contextual” input thatmay not be directly provided by the user via the user interface 1620.For example, user's interactions with the user interface 1620 areanalyzed using, e.g., natural language processing techniques, todetermine context or intent of the user, which may be treated in amanner similar to “direct” user input.

Depending on the type of the user device 1602, the computer-readablemedia 1610 can also optionally include other functional components anddata, such as other modules and data 1622, which can include programs,drivers, etc., and the data used or generated by the functionalcomponents. In addition, the computer-readable media 1610 can also storedata, data structures and the like, that are used by the functionalcomponents. Further, the user device 1602 can include many otherlogical, programmatic and physical components, of which those describedare merely examples that are related to the discussion herein.

In at least one example, the computer-readable media 1610 can includeadditional functional components, such as an operating system 1624 forcontrolling and managing various functions of the user device 1602 andfor enabling basic user interactions.

The communication interface(s) 1612 can include one or more interfacesand hardware components for enabling communication with various otherdevices, such as over the network(s) 1606 or directly. For example,communication interface(s) 1612 can enable communication through one ormore network(s) 1606, which can include, but are not limited any type ofnetwork known in the art, such as a local area network or a wide areanetwork, such as the Internet, and can include a wireless network, suchas a cellular network, a cloud network, a local wireless network, suchas Wi-Fi and/or close-range wireless communications, such as Bluetooth®,BLE, NFC, RFID, a wired network, or any other such network, or anycombination thereof. Accordingly, network(s) 1606 can include both wiredand/or wireless communication technologies, including Bluetooth®, BLE,Wi-Fi and cellular communication technologies, as well as wired or fiberoptic technologies. Components used for such communications can dependat least in part upon the type of network, the environment selected, orboth. Protocols for communicating over such networks are well known andwill not be discussed herein in detail.

Embodiments of the disclosure may be provided to users through a cloudcomputing infrastructure. Cloud computing refers to the provision ofscalable computing resources as a service over a network, to enableconvenient, on-demand network access to a shared pool of configurablecomputing resources that can be rapidly provisioned and released withminimal management effort or service provider interaction. Thus, cloudcomputing allows a user to access virtual computing resources (e.g.,storage, data, applications, and even complete virtualized computingsystems) in “the cloud,” without regard for the underlying physicalsystems (or locations of those systems) used to provide the computingresources.

The user device 1602 can further include one or more input/output (I/O)devices 1614. The I/O devices 1614 can include speakers, a microphone, acamera, and various user controls (e.g., buttons, a joystick, akeyboard, a keypad, etc.), a haptic output device, and so forth. The I/Odevices 1614 can also include attachments that leverage the accessories(audio-jack, USB-C, Bluetooth, etc.) to connect with the user device1602.

In at least one example, user device 1602 can include a display 1616.Depending on the type of computing device(s) used as the user device1602, the display 1616 can employ any suitable display technology. Forexample, the display 1616 can be a liquid crystal display, a plasmadisplay, a light emitting diode display, an OLED (organic light-emittingdiode) display, an electronic paper display, or any other suitable typeof display able to present digital content thereon. In at least oneexample, the display 1616 can be an augmented reality display, avirtually reality display, or any other display able to present and/orproject digital content. In some examples, the display 1616 can have atouch sensor associated with the display 1616 to provide a touchscreendisplay configured to receive touch inputs for enabling interaction witha graphic interface presented on the display 1616. Accordingly,implementations herein are not limited to any particular displaytechnology. Alternatively, in some examples, the user device 1602 maynot include the display 1616, and information can be presented by othermeans, such as aurally, hapticly, etc.

In addition, the user device 1602 can include sensor(s) 1618. Thesensor(s) 1618 can include a GPS device able to indicate locationinformation. Further, the sensor(s) 1618 can include, but are notlimited to, an accelerometer, gyroscope, compass, proximity sensor,camera, microphone, and/or a switch.

In some example, the GPS device can be used to identify a location of auser. In at least one example, the location of the user can be used bythe service provider 1512, described above, to provide one or moreservices. That is, in some examples, the service provider 1512 canimplement geofencing to provide particular services to users. As anexample, with a lending service, location can be used to confirm that astated purpose of a loan corresponds to evidence of use (e.g., Is theuser using the loan consistent with what he or she said he or she wasgoing to use it for?). Furthermore, in some examples, location can beused for payroll purposes. As an example, if a contractor completes aproject, the contractor can provide a geo-tagged image (e.g., taggedbased on location information availed by the GPS device). In someexamples, location can be used for facilitating peer-to-peer paymentsbetween nearby users 1514 and/or for sending users 1514 notificationsregarding available appointments with merchant(s) located proximate tothe users 1514. In at least one example, location can be used for takingpayments from nearby customers when they leave a geofence, or locationcan be used to initiate an action responsive to users 1514 enter abrick-and-mortar store of a merchant. Location can be used in additionalor alternative ways as well.

Additionally, the user device 1602 can include various other componentsthat are not shown, examples of which include removable storage, a powersource, such as a battery and power control unit, a barcode scanner, aprinter, a cash drawer, and so forth.

In addition, in some examples, the user device 1602 can include, beconnectable to, or otherwise be coupled to a reader device 1626, forreading payment instruments and/or identifiers associated with paymentobjects. In some examples, as described above, the reader device 1626can plug in to a port in the user device 1602, such as a microphoneport, a headphone port, an audio-jack, a data port, or other suitableport. In additional or alternative examples, the reader device 1626 canbe coupled to the user device 1602 via another wired or wirelessconnection, such as via a Bluetooth®, BLE, and so on. The reader device1626 can include a read head for reading a magnetic strip of a paymentcard, and further can include encryption technology for encrypting theinformation read from the magnetic strip. Additionally or alternatively,the reader device 1626 can be an EMV payment reader, which in someexamples, can be embedded in the user device 1602. Moreover, numerousother types of readers can be employed with the user device 1602 herein,depending on the type and configuration of the user device 1602.

The reader device 1626 may be a portable magnetic stripe card reader,optical scanner, smartcard (card with an embedded IC chip) reader (e.g.,an EMV-compliant card reader or short-range communication-enabledreader), RFID reader, or the like, configured to detect and obtain dataoff any payment instrument. Accordingly, the reader device 1626 mayinclude hardware implementation, such as slots, magnetic tracks, andrails with one or more sensors or electrical contacts to facilitatedetection and acceptance of a payment instrument. That is, the readerdevice 1626 may include hardware implementations to enable the readerdevice 1626 to interact with a payment instrument via a swipe (i.e., acard-present transaction where a customer slides a card having amagnetic strip through a payment reader that captures payment datacontained in the magnetic strip), a dip (i.e., a card-presenttransaction where a customer inserts a card having an embedded microchip(i.e., chip) into a payment reader first until the payment readerprompts the customer to remove the card), or a tap (i.e., a card-presenttransaction where a customer may tap or hover his or her electronicdevice such as a smart phone running a payment application over apayment reader to complete a transaction via short-range communication)to obtain payment data associated with a customer. Additionally oroptionally, the reader device 1626 may also include a biometric sensorto receive and process biometric characteristics and process them aspayment instruments, given that such biometric characteristics areregistered with the payment service system 100 and connected to afinancial account with a bank server.

The reader device 1626 may include processing unit(s), computer-readablemedia, a reader chip, a transaction chip, a timer, a clock, a networkinterface, a power supply, and so on. The processing unit(s) of thereader device 1626 may execute one or more modules and/or processes tocause the reader device 1626 to perform a variety of functions, as setforth above and explained in further detail in the following disclosure.In some examples, the processing unit(s) may include a centralprocessing unit (CPU), a graphics processing unit (GPU), a CPU and aGPU, or processing units or components known in the art. Additionally,each of the processing unit(s) may possess its own local memory, whichalso may store program modules, program data, and/or one or moreoperating systems. Depending on the exact configuration and type of thereader device 1626, the computer-readable media may include volatilememory (such as RAM), non-volatile memory (such as ROM, flash memory,miniature hard drive, memory card, or the like), or some combinationthereof. In at least one example, the computer-readable media of thereader device 1626 may include at least one module for performingvarious functions as described herein.

The reader chip may perform functionalities to control the operationsand processing of the reader device 1626. That is, the reader chip mayperform functionalities to control payment interfaces (e.g., acontactless interface, a contact interface, etc.), a wirelesscommunication interface, a wired interface, a user interface (e.g., asignal condition device (FPGA)), etc. Additionally, the reader chip mayperform functionality to control the timer, which may provide a timersignal indicating an amount of time that has lapsed following aparticular event (e.g., an interaction, a power-down event, etc.).Moreover, the reader chip may perform functionality to control the clock166, which may provide a clock signal indicating a time. Furthermore,the reader chip may perform functionality to control the networkinterface, which may interface with the network(s) 1606, as describedbelow.

Additionally, the reader chip may perform functionality to control thepower supply. The power supply may include one or more power suppliessuch as a physical connection to AC power or a battery. Power supply mayinclude power conversion circuitry for converting AC power andgenerating a plurality of DC voltages for use by components of readerdevice 1626. When power supply includes a battery, the battery may becharged via a physical power connection, via inductive charging, or viaany other suitable method.

The transaction chip may perform functionalities relating to processingof payment transactions, interfacing with payment instruments,cryptography, and other payment-specific functionality. That is, thetransaction chip may access payment data associated with a paymentinstrument and may provide the payment data to a POS terminal, asdescribed above. The payment data may include, but is not limited to, aname of the customer, an address of the customer, a type (e.g., credit,debit, etc.) of a payment instrument, a number associated with thepayment instrument, a verification value (e.g., PIN Verification KeyIndicator (PVKI), PIN Verification Value (PVV), Card Verification Value(CVV), Card Verification Code (CVC), etc.) associated with the paymentinstrument, an expiration data associated with the payment instrument, aprimary account number (PAN) corresponding to the customer (which may ormay not match the number associated with the payment instrument),restrictions on what types of charges/debts may be made, etc.Additionally, the transaction chip may encrypt the payment data uponreceiving the payment data.

It should be understood that in some examples, the reader chip may haveits own processing unit(s) and computer-readable media and/or thetransaction chip may have its own processing unit(s) andcomputer-readable media. In other examples, the functionalities ofreader chip and transaction chip may be embodied in a single chip or aplurality of chips, each including any suitable combination ofprocessing units and computer-readable media to collectively perform thefunctionalities of reader chip and transaction chip as described herein.

While, the user device 1602, which can be a POS terminal, and the readerdevice 1626 are shown as separate devices, in additional or alternativeexamples, the user device 1602 and the reader device 1626 can be part ofa single device, which may be a battery-operated device. In such anexample, components of both the user device 1602 and the reader device1626 may be associated with the single device. In some examples, thereader device 1626 can have a display integrated therewith, which can bein addition to (or as an alternative of) the display 1616 associatedwith the user device 1602.

The server(s) 1604 can include one or more servers or other types ofcomputing devices that can be embodied in any number of ways. Forexample, in the example of a server, the modules, other functionalcomponents, and data can be implemented on a single server, a cluster ofservers, a server farm or data center, a cloud-hosted computing service,a cloud-hosted storage service, and so forth, although other computerarchitectures can additionally or alternatively be used.

Further, while the figures illustrate the components and data of theserver(s) 1604 as being present in a single location, these componentsand data can alternatively be distributed across different computingdevices and different locations in any manner. Consequently, thefunctions can be implemented by one or more server computing devices,with the various functionality described above distributed in variousways across the different computing devices. Multiple server(s) 1604 canbe located together or separately, and organized, for example, asvirtual servers, server banks and/or server farms. The describedfunctionality can be provided by the servers of a single merchant orenterprise, or can be provided by the servers and/or services ofmultiple different customers or enterprises.

In the illustrated example, the server(s) 1604 can include one or moreprocessors 1628, one or more computer-readable media 1630, one or moreI/O devices 1632, and one or more communication interfaces 1634. Eachprocessor 1628 can be a single processing unit or a number of processingunits, and can include single or multiple computing units or multipleprocessing cores. The processor(s) 1628 can be implemented as one ormore microprocessors, microcomputers, microcontrollers, digital signalprocessors, central processing units, state machines, logic circuitries,and/or any devices that manipulate signals based on operationalinstructions. For example, the processor(s) 1628 can be one or morehardware processors and/or logic circuits of any suitable typespecifically programmed or configured to execute the algorithms andprocesses described herein. The processor(s) 1628 can be configured tofetch and execute computer-readable instructions stored in thecomputer-readable media 1630, which can program the processor(s) 1628 toperform the functions described herein.

The computer-readable media 1630 can include volatile and nonvolatilememory and/or removable and non-removable media implemented in any typeof technology for storage of information, such as computer-readableinstructions, data structures, program modules, or other data. Suchcomputer-readable media 1630 can include, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, optical storage,solid state storage, magnetic tape, magnetic disk storage, RAID storagesystems, storage arrays, network attached storage, storage areanetworks, cloud storage, or any other medium that can be used to storethe desired information and that can be accessed by a computing device.Depending on the configuration of the server(s) 1604, thecomputer-readable media 1630 can be a type of computer-readable storagemedia and/or can be a tangible non-transitory media to the extent thatwhen mentioned, non-transitory computer-readable media exclude mediasuch as energy, carrier signals, electromagnetic waves, and signals perse.

The computer-readable media 1630 can be used to store any number offunctional components that are executable by the processor(s) 1628. Inmany implementations, these functional components comprise instructionsor programs that are executable by the processors 1628 and that, whenexecuted, specifically configure the one or more processors 1628 toperform the actions attributed above to the service provider 1512 and/orpayment processing service. Functional components stored in thecomputer-readable media 1630 can optionally include a subscriptionmodule 112, a payment processing module 114, as described above withreference to FIG. 1, a training module 1636, and one or more othermodules and data 1638.

In at least one example, in addition to the functionality describedabove with reference to the payment processing module 114, the paymentprocessing module 114 can be configured to receive transaction data fromPOS systems, such as the POS system 1524 described above with referenceto FIG. 15. The payment processing module 114 can transmit requests(e.g., authorization, capture, settlement, etc.) to payment serviceserver computing device(s) to facilitate POS transactions betweenmerchants and customers. The payment processing module 114 cancommunicate the successes or failures of the POS transactions to the POSsystems. The merchant module

The training module 1636 can be configured to train models usingmachine-learning mechanisms. For example, a machine-learning mechanismcan analyze training data to train a data model that generates anoutput, which can be a recommendation, a score, and/or anotherindication. Machine-learning mechanisms can include, but are not limitedto supervised learning algorithms (e.g., artificial neural networks,Bayesian statistics, support vector machines, decision trees,classifiers, k-nearest neighbor, etc.), unsupervised learning algorithms(e.g., artificial neural networks, association rule learning,hierarchical clustering, cluster analysis, etc.), semi-supervisedlearning algorithms, deep learning algorithms, etc.), statisticalmodels, etc. In at least one example, machine-trained data models can bestored in a data store associated with the user device(s) 1602 and/orthe server(s) 1604 for use at a time after the data models have beentrained (e.g., at runtime).

The one or more other modules and data 1638 can include programs,drivers, etc., and the data used or generated by the functionalcomponents. Further, the server(s) 1604 can include many other logical,programmatic and physical components, of which those described above aremerely examples that are related to the discussion herein.

The one or more “modules” referenced herein may be implemented as moremodules or as fewer modules, and functions described for the modules maybe redistributed depending on the details of the implementation. Theterm “module,” as used herein, refers broadly to software stored onnon-transitory storage medium (e.g., volatile or non-volatile memory fora computing device), hardware, or firmware (or any combination thereof)modules. Modules are typically functional such that they that maygenerate useful data or other output using specified input(s). A modulemay or may not be self-contained. An application program (also called an“application”) may include one or more modules, or a module may includeone or more application programs that can be accessed over a network ordownloaded as software onto a device (e.g., executable code causing thedevice to perform an action). An application program (also called an“application”) may include one or more modules, or a module may includeone or more application programs. In additional and/or alternativeexamples, the module(s) may be implemented as computer-readableinstructions, various data structures, and so forth via at least oneprocessing unit to configure the computing device(s) described herein toexecute instructions and to perform operations as described herein.

In some examples, a module may include one or more APIs to perform someor all of its functionality (e.g., operations). In at least one example,a SDK can be provided by the service provider to allow third-partydevelopers to include service provider functionality and/or availservice provider services in association with their own third-partyapplications. Additionally or alternatively, in some examples, theservice provider can utilize a SDK to integrate third-party serviceprovider functionality into its applications. That is, API(s) and/orSDK(s) can enable third-party developers to customize how theirrespective third-party applications interact with the service provideror vice versa.

The computer-readable media 1630 can additionally include an operatingsystem 1640 for controlling and managing various functions of theserver(s) 1604.

The communication interface(s) 1634 can include one or more interfacesand hardware components for enabling communication with various otherdevices, such as over the network(s) 1606 or directly. For example,communication interface(s) 1634 can enable communication through one ormore network(s) 1606, which can include, but are not limited any type ofnetwork known in the art, such as a local area network or a wide areanetwork, such as the Internet, and can include a wireless network, suchas a cellular network, a local wireless network, such as Wi-Fi and/orclose-range wireless communications, such as Bluetooth®, BLE, NFC, RFID,a wired network, or any other such network, or any combination thereof.Accordingly, network(s) 1602 can include both wired and/or wirelesscommunication technologies, including Bluetooth®, BLE, Wi-Fi andcellular communication technologies, as well as wired or fiber optictechnologies. Components used for such communications can depend atleast in part upon the type of network, the environment selected, orboth. Protocols for communicating over such networks are well known andwill not be discussed herein in detail.

The server(s) 1604 can further be equipped with various I/O devices1632. Such I/O devices 1632 can include a display, various userinterface controls (e.g., buttons, joystick, keyboard, mouse, touchscreen, biometric or sensory input devices, etc.), audio speakers,connection ports and so forth.

In at least one example, the system 1600 can include a data store 1642that can be configured to store data that is accessible, manageable, andupdatable. In some examples, the data store 1642 can be integrated withthe user device 1602 and/or the server(s) 1604. In other examples, asshown in FIG. 16, the data store 1642 can be located remotely from theserver(s) 1604 and can be accessible to the server(s) 1604. The datastore 1642 can comprise multiple databases and/or servers connectedlocally and/or remotely via the network(s) 1606.

In at least one example, the data store 1642 can store data as describedabove with reference to FIG. 1 (e.g., profile(s) 116, inventory data118, transaction data 120). Furthermore, in at least one example, thedata store 1642 can store catalog database(s). A catalog can store dataassociated with items that a merchant has available for acquisition. Thedata store 1642 can store additional or alternative types of data asdescribed herein.

The phrases “in some examples,” “according to various examples,” “in theexamples shown,” “in one example,” “in other examples,” “variousexamples,” “some examples,” and the like generally mean the particularfeature, structure, or characteristic following the phrase is includedin at least one example of the present invention, and may be included inmore than one example of the present invention. In addition, suchphrases do not necessarily refer to the same examples or to differentexamples.

If the specification states a component or feature “can,” “may,”“could,” or “might” be included or have a characteristic, thatparticular component or feature is not required to be included or havethe characteristic.

Further, the aforementioned description is directed to devices andapplications that are related to payment technology. However, it will beunderstood, that the technology can be extended to any device andapplication. Moreover, techniques described herein can be configured tooperate irrespective of the kind of payment object reader, POS terminal,web applications, mobile applications, POS topologies, payment cards,computer networks, and environments.

Various figures included herein are flowcharts showing example methodsinvolving techniques as described herein. The methods illustrated aredescribed with reference to FIGS. 1-6, 15, and 16 for convenience andease of understanding. However, the methods illustrated are not limitedto being performed using components described in FIGS. 1-6, 15, and 16,and such components are not limited to performing the methodsillustrated herein.

Furthermore, the methods described above are illustrated as collectionsof blocks in logical flow graphs, which represent sequences ofoperations that can be implemented in hardware, software, or acombination thereof. In the context of software, the blocks representcomputer-executable instructions stored on one or more computer-readablestorage media that, when executed by processor(s), perform the recitedoperations. Generally, computer-executable instructions includeroutines, programs, objects, components, data structures, and the likethat perform particular functions or implement particular abstract datatypes. The order in which the operations are described is not intendedto be construed as a limitation, and any number of the described blockscan be combined in any order and/or in parallel to implement theprocesses. In some embodiments, one or more blocks of the process can beomitted entirely. Moreover, the methods can be combined in whole or inpart with each other or with other methods.

What is claimed is:
 1. A method, implemented at least in part by acomputing system of a payment processing service provider, the methodcomprising: receiving, by the computing system, first transaction dataassociated with (i) brick-and-mortar transactions between a customer andmerchants associated with the payment processing service provider and(ii) ecommerce transactions between the customer and the merchants;processing, by the computing systems, first payments associated with thefirst transaction data; receiving, by the computing system, secondtransaction data associated with a second transaction between thecustomer and a merchant of the merchants; determining, by the computingsystem and based at least in part on the first transaction data and thesecond transaction data, that the customer has purchased instances of anitem at a substantially regular interval; determining, by the computingsystem, a recommendation to offer a subscription to enable the customerto periodically access additional instances of the item; causing, by thecomputing system, the recommendation to be presented to the customer;and responsive to receiving an indication that the customer accepts therecommendation, associating, by the computing system, the subscriptionwith a profile of the customer; and processing, by the computing system,a second payment associated with the second transaction data.
 2. Themethod as claim 1 recites, wherein the recommendation is associated withan incentive that enables the customer to purchase the additionalinstances of the item at a discount.
 3. The method as claim 1 recites,wherein the recommendation is presented to the customer via a display ofa point-of-sale device at a brick-and-mortar location of the merchant,in association with a brick-and-mortar transaction.
 4. The method asclaim 1 recites, wherein the recommendation is presented to the customervia a display of a device of the customer, in association with anecommerce transaction.
 5. The method as claim 1 recites, wherein therecommendation is associated with an actuation mechanism to accept therecommendation and activate the subscription via a single interaction,and the indication is received responsive to actuation of the actuationmechanism.
 6. The method as claim 1 recites, further comprising:accessing, from the profile of the customer, payment data associatedwith (i) a linked bank account or (ii) an account maintained by thepayment processing service provider; and processing a third payment fora cost of at least a portion of the subscription based at least in parton the payment data.
 7. A system comprising: one or more processors; andone or more computer-readable media that, when executed by the one ormore processors, cause the system to perform operations comprising:receiving first transaction data associated with first transactionsbetween a customer and a plurality of merchants that process the firsttransactions via a computing system of a payment processing service;processing first payments associated with the first transaction data;receiving second transaction data associated with a second transactionbetween the customer and a merchant of the plurality of merchants;determining, based at least in part on the first transaction data andthe second transaction data, that the customer purchased a first item ata first time; determining, based at least in part on the secondtransaction data, that the customer purchased a second item at a secondtime; determining that the customer is eligible for a subscription toenable the customer to receive a third item at a third time; causing arecommendation of an offer for the subscription to be presented to thecustomer; associating the subscription with a profile of the customer;and processing a second payment associated with the second transactiondata.
 8. The system as claim 7 recites, wherein the first transactionsare associated with at least one of: one or more brick-and-mortartransactions; or one or more ecommerce transactions.
 9. The system asclaim 7 recites, wherein the first item, the second item, and the thirditem are instances of a same item.
 10. The system as claim 7 recites,further comprising presenting a graphical user interface via a deviceoperable by the customer, wherein the graphical user interface enablesthe customer to manage the subscription and one or more othersubscriptions associated with the plurality of merchants.
 11. The systemas claim 7 recites, wherein the subscription is associated with thepayment processing service, the third time is associated with afulfillment event, and the operations further comprise: generating,prior to the third time, an order that includes the third item;determining that a first merchant associated with the payment processingservice is unable to fulfill the order; reserving, based at least inpart on the order, the third item in an inventory of a second merchantassociated with the payment processing service; processing a thirdpayment for the order; determining, based at least in part on processingthe third payment for the order, that a cost of the order is satisfied;and processing the order based at least in part on the cost of the orderbeing satisfied.
 12. The system as claim 7 recites, wherein thesubscription is associated with the merchant of the plurality ofmerchants, the third time is associated with a fulfillment event, andthe operations further comprise: generating, prior to the third time, anorder that includes the third item; reserving, based at least in part onthe order, the third item in an inventory of the merchant; processing athird payment for the order; determining, based at least in part onprocessing the third payment for the order, that a cost of the order issatisfied; and processing the order based at least in part on the costof the order being satisfied.
 13. The system as claim 7 recites, theoperations further comprising: accessing, from the profile of thecustomer, payment data associated with (i) a linked bank account or (ii)an account maintained by the payment processing service; and processinga third payment for a cost of at least a portion of the subscriptionbased at least in part on the payment data.
 14. The system as claim 7recites, wherein the first item and the second item are instances of asame item and the operations further comprise determining, based atleast in part on the first time and the second time, that the customerpurchases the instances of the same item at a substantially regularinterval.
 15. The system as claim 14 recites, the operations furthercomprising: determining, based at least in part on the first transactiondata or the second transaction data, that the customer purchased afourth item at a fourth time prior to the third time, and whereindetermining that the customer purchases the instances of the same itemat the substantially regular interval is based at least in part ondetermining that a first period of time between the first time and thesecond time differs by less than a threshold from a second period oftime between the fourth time and either the first time or the secondtime.
 16. A method, implemented at least in part by a computing systemof a payment processing service provider, the method comprising:receiving first transaction data associated with first transactionsbetween a customer and a plurality of merchants; processing, by thecomputing systems, first payments associated with the first transactiondata; receiving second transaction data associated with a secondtransaction between the customer and a merchant of the plurality ofmerchants; determining, based at least in part on the first transactiondata, that the customer purchased a first item at a first time;determining, based at least in part on the second transaction data, thatthe customer purchased a second item at a second time, wherein the firstitem and the second item are instances of a same item or item type;determining that the customer is eligible for a subscription to enablethe customer to receive a third item at a third time; causing, prior toprocessing a second payment for the second transaction, a recommendationof an offer for the subscription to be presented to the customer;associating the subscription with a profile of the customer; andprocessing, based at least in part on the second transaction data, thesecond payment for the second transaction.
 17. The method as claim 16recites, further comprising, responsive to associating the subscriptionwith the profile of the customer, crediting an account of the customerfor one or more previous transactions associated with instances of thethird item.
 18. The method as claim 16 recites, recites, wherein thesubscription is associated with the profile of the customer withoutinput from the customer and the method further comprises: receiving arequest to cancel the subscription; and disassociating the subscriptionand the profile of the customer responsive to receiving the request. 19.The method as claim 16 recites, further comprising determining at leastone related item to bundle with the third item in the subscription,wherein the subscription is for the third item and the at least onerelated item.
 20. The method as claim 16 recites, further comprising:receiving, at a time after the subscription is associated with theprofile of the customer, a request to cancel the subscription; andcausing a subsequent offer for the subscription to be presented to thecustomer, wherein the subsequent offer is associated with an incentiveto discourage the customer from cancelling the subscription.